Hi all, I have an application which needs to connect to a tcp/ip server and receive messages from it. However, the application will not be sitting idly by just waiting for these messages and it is interested in receiving the messages only when in a certain state (when a particular form is open).
Meanwhile, the user may be doing other things at which time, the application is as I mentioned, not interested in processing these messages. I am wondering if I should: 1. Use a TCP/IP server and have the client application connect and disconnect determine by its state and if it is interested in receiving the events. 2. Use TCP/IP as above, but do not connect/disconnect repeatedly, but instead send a message to the server that it is temporarily unavailable. This would save on setting up and tearing down connections and I wouldn't have to worry about running of the available tcp/ip connections on Windows. 3. Use UDP broadcast from the server to notify the clients and just let the clients determine if they want to pay attention to the message or not. Any advise or suggestions? Thanks, -- Warm Regards, Lee ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
