The conditions of the problem:
1. There is a server under Windows Server 2008R2 Enterprise.
2. As a "combat" web server there is running IIS 7.0
I want to make so that for a particular IIS website I am forwarding a GET request to /daemon
to a local service (for connection to a socket or something else), and other requests fulfilled independently.
The connection itself should not be closed: the local service will play the role of Comet-like demon, and to give the message stream for a long time.
Moreover, the whole structure has to withstand several thousand simultaneously open sessions to the daemon + to work out the usual requests for static content and server-side logic.
So to bother you have that would not have problems with firewalls and cross-domain security in JavaScript. For the ultimate browser that the request to the daemon, just the web server must be identical — same domain, same port, only the URI is different.
In UNIX-like systems this problem was solved by writing modules for nginx and Apache, but in programming in General and Windows .NET in particular I'm not good unfortunately :(.
You solve such a problem, in principle?
Google suggest NET.TCP Port Sharing (
http://msdn.microsoft.com/en-us/library/ms734772.aspx).
If this technology is to solving the problem?
Or maybe there are more simple variants?
