I am working on a project , client server based live meeting.
I connected two systems in same network. The system is sending mail to each other but cannot join in chat at same time .
I don't know exactly how to configure and connect web browser with server so that it can communicate.
What will be the problem not allowing to chat and please suggest any method to overcome this fault.
In desperate need of help..
Database is connected
You could use SignalR as a possible solution. It allows real-time functionality on your web site.
Take a look here: IM using SignalR
Related
I have my own application. This application use the zigbee2mqtt service running on the server.
I want to add homeassistant on the same server.
The server is a Raspberry with a zigbee USB stick connected.
However, it seems that using both in the same time doesn't work.
Either it works for my application, either it works for home assistant.
Someone has an idea how to deal with it ?
Does I need to buy an other zigbee USB stick (one for my own application, and one for Home assistant ?)
Thanks
The solution found is the following :
Use the homeassistant (supervisor) to have the feature to add the zigbee2mqtt add-on (here).
Once it's successfully configured, the zigbee2mqtt service run in home assistant.
And you can send mqtt messages to the service from homeassistant (via the existing integration). Also, you can send mqtt messages from my own application.
It works !
My previous experience with SignalR was only as a server, getting data from a database and then updating the webpages accordingly.
I was wondering if it is possible to use SignalR to connect to other servers that shares data via Websockets and then consolidating the data to send out to your own clients, also using SignalR? So something like a forwarder of sorts.
You can use the .net signalR client to hook nearly anything to the server. There can be difficulties with waking the server up, so it is important to check the behavior.
https://learn.microsoft.com/en-us/aspnet/core/signalr/dotnet-client?view=aspnetcore-5.0&tabs=visual-studio
I am in a stage of using SignalR in my project and i don't understand when to use Self hosted option and when we should not use. As a example if I am willing to host my web application in server farm,
There will be separate hosting servers
Separate SignalR hubs in each IIS server
If we want to broadcast message into each client, how this is working in SignalR
The idea with SignalR running in multiple instances is that clients connected on instance A cannot get messages from clients connected to instance B.
(SignalR scaleout documentation)
However, when you scale out, clients can get routed to different
servers. A client that is connected to one server will not receive
messages sent from another server.
The solution to this is using a backplane - everytime a server recieves a message, it forwards it to all other servers. You can do this using Azure Service Bus, Redis or SQL.
The way I see, you use the self host option when you either don't want the full IIS running (because you have some lightweight operations that don't require all IIS heaviness) or you don't want a web server at all (for example you want to add real-time functionality to an already existing let's say forms application, or in any other process).
Be sure to read the documentation for self-hosting SignalR and decide whether you actually need to self host SignalR.
If you are developing a web application under IIS, I don't see any reason why you would want to self-host SignalR.
Hope this helps. Best of luck!
I want to create a socket on the client to listen for notifications from the server. Is there any example of a socket server built that I can use in my asp.net application?
Asp.net is state-less you would need to build a windows service or windows application to publish a socket end-point unless you are looking at something like Comet?
Asp.net cannot fire server events if there is no intervention by a process or a user.
Can you describe your requirement a bit better?
https://github.com/SignalR/SignalR is a Server side and client side implementation of Comet it looks like a suitable solution for messaging purposes what are you attempting to build this might give more insight to a suitable solution.
So i want to to create a web application using asp.net to connect to another application (for example a simple windows form) using sockets. The problem is i'm behind firewall and i don't have the authority to mess with the firewall settings, what other options can i do besides sockets?
My application is fairly simple, the web application will be hosted on the internet and has a "connect" button, when its click it establish connection with the windows form that is on another computer and display the message "Connected" if its connected. All this will be tested behind some kind of corporal firewall. How do i get around this?
The firewall is there specifically to stop this kind of thing.
The bestway around it would be to have the Forms app poll the server for connectivity - this can be made to look near real time by making the server receive the request, then wait until it gets a connect action, or time out after a few minutes and return nothing. Then the forms app would request again.
I think instead of using directly a web application, you should look forward to create a web service to solve both the purposes. You can have its reference in both of them. your Web Form will make a request to connect to the web service instead of application. That will solve both purposes.