Yeah this should be fine. Basically you are opening a HttpWebRequest and keeping it alive so that you can have a connection between IIS and Client B.
The only issue I can see with this is does it support two-way communication? If it does than everything is sweet, otherwise it may prove expensive if Client B has to reconnect every time it needs to do a send/receive. I suppose only testing will answer this question. -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Steve Welborn Sent: Friday, 15 July 2005 12:19 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Need advice on my Theory of Two way communication Remoting Chris, Thanks for the reply and time on this theory. Basically what you discribed is kinda what im doing now, except for holding an active connection. What I propose is instead of clientB asking if there is data, IIS uses that active Connection that it is holding and sends the data to ClientB. Other than that, you pretty much have what I am saying. Do you think this is possible with ClientB being outbound only? ClientB would be the one initiating the call, IIS would be sending back HTTP like commands (see my first post for example) so the firewall would just assume it ws a reply from a website. I mean, if my theory is right. Thanks again ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by NetIQ MailMarshal ##################################################################################### =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
