I have two apps under same domain http://mydomain.com/App1 & http://mydomain.com/App2 configured with SignalR.
i have my hub class(server asp.net c# class) setup at App1.
And i have my signalR javascript clients setup at App1 and App2.
For App2 i am connecting to hub, setup at App1 (included in my Index html file as javascript src=/mydomain/App1/SignalR/hubs).
When i try to send a message from server to clients (app1 & app2), i am able to see it only in app1 and not in app2. But when i send a message from client app2 to server app1 i am able to get that message in app1.
There is only one-way comm. from client to server. Any reasons why is it so?
Related
I have an application that uses SignalR to broadcast data to all connected clients. Its a .NET6 Blazor Wasm hosted web application. Now, I want the the broadcaster (which is running on the Blazor server) to connect to a data source that is outside my website, and get data from there. The source data is being broadcast via UDP on a different network.
So my question is, is it possible that my SignalR hub that is running on the Blazor server connects to another SignalR hub running on a different machine in a different network and get real time data from it? Or may be I can run a SignalR client as well on my Blazor server and then connect to a machine on another network? Can I run a SignalR hub on the UDP source machine to which my Blazor server SignalR hub or client can connect? From what I have read, SignalR only runs on a website. Or is it that SignalR is not suitable for this kind of server to server data feeds?
If I have a blazor server app hosted on a server (Server A) and a client is accessing that server from another device (Client A).
If the Blazor server app is calling a webservice via a System.Net.Http.HttpClient call that is hosted on another server (Server B). Will the request originate from the client device (Client A) or the server hosting the Blazor server app (Server A)?
This has implications for network access requirements as Client may not have access to the webservice hosted on Server B but Server A does?
With Blazor Server, all c# code is executed on the server, including your web request with System.Net.Http.HttpClient.
This differs from Blazor WASM which runs entirely on the client (after the initial request to Server A for the app).
We are setting up on premises ADFS and WAP servers.
We are using a SSL cert shared between the SDFS server and WAP.
We are using split brain DNS so that the internal clients point to the ADFS server and the external users get routed to the WAP.
The ADFS service name is the external DNS name and is different than the host name.
The MVC web application has been published on the WAP.
Internal clients get routed to the ADFS server login page and get authenticated correctly. The external clients get routed to the login page but a TCP rst gets sent to the client immediately. I can't find any logs in the event viewer to help troubleshoot this.
Can someone offer a suggestion?
Our client has a requirement that a web server can only have port 80 and 443 open, both public and internal facing, but our application would benefit from using queuing on the inside.
Is it possible to run RabbitMQ over port 80?
Update
The setup is as follows.
We have a public facing API server which calls various back end systems.
In between the API server and the back end servers there is another layer which in most cases just works like a proxy.
Some of the back end systems, as well as the proxy layer, go up and down intermittently.
What I would like to do is have a queue on the API server, a queue in the proxy layer and a queue in the back end layer.
These queues would be federated so that a messages placed on the queue on the API server would be forwarded all the way down to the back end servers (queuing is needed for inserts and updates only).
One way is using Web-Stomp plugin and Sock.js, using nginx as proxy.
Another way - node.js callback for some sending messages, handling events and create messages with node.js.
Server side works with RabbitMQ by localhost connect with default port.
Third way is using subdomain with another IP adress.
Here is my situation:
I have a 4-tier web application consisting of browser, web server, application servers and database.
Browser and application server should communicate in a RPC-style way.
The backend will run on windows machines, so I will use IIS as web server The application needs real time communication between application server and browser.
I want to use a SignalR connection for the communication between browser and web server. For the communication between web server and application server's I want to use a plain TCP connection.
I think this approach will enable me to send JSON messages between browser and application servers. But how can I realize a RPC communication?
Can I write a SignalR Hub, generate a JS proxy and bind the Hub to a TCP socket?
Here is a picture: https://www.dropbox.com/s/xeaja4dos4bgvbz/SignalR_Hubs_Stackoverflow.png
Nope. SignalR is based on HTTP not TCP directly. WebSockets is the closest thing to a raw tcp socket and it has the added benefit that it works over port 80.