Advertisement
Hi
I want to implement the following:
Any request from browser with a .conn extention should be stored. ( www.somewebsite.com/somedir/somefile.conn )
the somefile.conn should not be really present in the directory so IIS should not check if the file excists.Rather the filename requested should be stored with the request.
So what is being gathered is a collection of requests ( stil open and alive, I mean persistent http connection ) and the name of the file they used ( in this example somefile.conn ) [Usually when someone visits the site, the connection opens with the server over http, response gets sent to the browser and the connection closes... In case of persistent connection, the connection does not close but keeps alive... this prevent page refresh if later the server sends more response to the browser... (you can also see it as a chat application via the browser without page refresh) ]
Then the ASP.NET application should be able to send a response to every request that was stored requesting a particular filename ( in this example somefile.conn ). And some moments later the ASP.NET application can send a response to all requests that requested some other file like otherfile.conn
And at any other time the ASP.NET application can respond to the connections that requested any other files like in this example somefile.conn that are still very much alive and open just like all the other requests that are stored.
In other words:
We do not want ISAPI filter but want to use httphandler / httpmodule and perhaps this kind of thing can be done via tcplistener, httpwebrequest, httpwebresponse and/or sockets.
I want to create a system whereby if anybody visits my site the request connection should not be closed but remain active (keepalive) somewhere in a collection.
The reason I want to store the request somewhere is to be able to respond to the collected requests (any or all) at any given time.
The handler/module (initially I thought ISAPI) should be able to receive a string from the ASP.NET application and send that string as a response to the stored requests. However the requests should NOT close after being responded to and they SHOULD be kept alive. Because subsequent responses can be made at any given time.
Basically, I need a module to collect the requests (persistent connection) and keep them in a collection along with the filename requested... Another class/module should be able to respond to the group of x.conn or y.conn requests by the string I send to the class/module...
Thanks
Timsi
I want to implement the following:
Any request from browser with a .conn extention should be stored. ( www.somewebsite.com/somedir/somefile.conn )
the somefile.conn should not be really present in the directory so IIS should not check if the file excists.Rather the filename requested should be stored with the request.
So what is being gathered is a collection of requests ( stil open and alive, I mean persistent http connection ) and the name of the file they used ( in this example somefile.conn ) [Usually when someone visits the site, the connection opens with the server over http, response gets sent to the browser and the connection closes... In case of persistent connection, the connection does not close but keeps alive... this prevent page refresh if later the server sends more response to the browser... (you can also see it as a chat application via the browser without page refresh) ]
Then the ASP.NET application should be able to send a response to every request that was stored requesting a particular filename ( in this example somefile.conn ). And some moments later the ASP.NET application can send a response to all requests that requested some other file like otherfile.conn
And at any other time the ASP.NET application can respond to the connections that requested any other files like in this example somefile.conn that are still very much alive and open just like all the other requests that are stored.
In other words:
We do not want ISAPI filter but want to use httphandler / httpmodule and perhaps this kind of thing can be done via tcplistener, httpwebrequest, httpwebresponse and/or sockets.
I want to create a system whereby if anybody visits my site the request connection should not be closed but remain active (keepalive) somewhere in a collection.
The reason I want to store the request somewhere is to be able to respond to the collected requests (any or all) at any given time.
The handler/module (initially I thought ISAPI) should be able to receive a string from the ASP.NET application and send that string as a response to the stored requests. However the requests should NOT close after being responded to and they SHOULD be kept alive. Because subsequent responses can be made at any given time.
Basically, I need a module to collect the requests (persistent connection) and keep them in a collection along with the filename requested... Another class/module should be able to respond to the group of x.conn or y.conn requests by the string I send to the class/module...
Thanks
Timsi
Advertisement
Advertisement