Posted by Jim Guerber on February 08, 2007 at 15:36:01:
In Reply to: Sending MSG to Comet session on another PC posted by Mike Saunders on February 05, 2007 at 11:31:11:
There are several complex problems with implementing a message function across our network.
1. Identification -- There may be more than one server involved. There may be more than one session with the same node/partition$/term$. How do we identify the particular target.
2. Even implementing a broadcast type of message is not trivial. The server model we use is a strict client/server architecture. The client is not prepared to receive and process a message from the server until/unless it first sends a request.
I am NOT saying that we won't do this. We have thought about this problem for several years. I am just saying that it is not an easy thing to accomplish.
This may be easier for you to accomplish in your application programs. Make a common file to hold messages. At the entrance to all of your programs put a piece of code that looks for this user's particular message in the keyed file and if it is present, display it in a message box and delete the record from the file.