That is correct. Unless you find a way to maintain the socket across Page
postbacks / callbacks, it would not work. I suppose you could try storing the
socket in Session, or making it a static public property in Global.
-- Peter
Site:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
MetaFinder:
http://www.blogmetafinder.com
"Dav Tan" wrote:
Quote:
Here is the situation, we have a old server application using TCP/IP socket
communication. Right now, we need to build a ASP.NET web application to be
the front-end client to talk to the server application. A complete
communicate will happen back & forth between the ASP.net page and server
application several times. I think the issue here is state management. My
question is: is there a good way to do it? Or is there a kind of
architecture to do this?
>
BTW, I read one user's response to a similar question in the forum: " there
will be no difference between using tcp/ip socket in a window form and
calling from asp.net page". I think this is wrong, the big difference is
"State management".
>
Thanks,
DT
>
>
>
