I have to interface to a third-party application that receives HTTP
POSTs with XML content to a certain port on the server. The server is
*not* a web server, rather some custom server app written by the
third-party, so it's behavior is not predictable or necessarily HTTP
compliant. Therefore, I can't use the much simpler HttpWebRequest.
Also, if I repeatedly open new connections to it, the server gets
bogged down with authentication and crashes.
So, in order for my web service front-end to work properly, I need to
take many incoming requests and consolidate them to one TCP connection
that is already authenticated by parsing some cookie value that gets
returned with the first request and gets sent with all future requests.
I may also have to connect using SSL, so I was thinking of purchasing
the PowerTCP SSL Sockets control from dart.com.
The scenario:
1) Windows Server 2003 Web running IIS
2) Many async requests made to .Net web services
3) All services use one custom SSL TCP connection to talk to back end:
Should I just create a static member to do this?
4) Responses come back over single TCP connection: How will these go
back to the proper web service call?
5) If the response has more than X rows, it sends a continuation cookie
with which I need to make a second request and it'll send the next X
rows. So, I have to do this repeatedly until all rows received and
then return the web service call.
Any ideas for the problems above and clues on where I should look for
more information?
