The old way involved having a listener running on a known port, which would job off a new MUMPS process for each CPRS client.
Since the new MUMPS process created a new TCP/IP outgoing socket from the server, the listener only had a minimal load per CPRS client, and thus didn't have to hand off the socket (which is not in the MUMPS standard) nor did it have to start a new listener on the known port, (with the potential of missing a CPRS client connection) when the new listener was "taking over". Unfortunately, the old method didn't work when connecting a CPRS client within a NAT or router to a server that also could be within a NAT or router. Since the CPRS client machine had a non-routeable address in that case, it was the equivalent of trying to contact someone by phone where you had their phone extension, but not the main trunk number. The new CPRS process follows the idea that if you can get a socket between the CPRS client and the server, you should simply use that socket. The expectation is that using inetd/xinetd to handle known port management would yield no "dropped connections". David 713-870-3834 > > Unfortunately, I don't know the details on how to connect to the new > CPRS GUI, but I know that it works with a GT.M server deployed under > inetd/xinetd, but hopefully someone on this list will be able to tell > you how. > > I also don't know why the protocol was changed/enhanced. > > -- Bhaskar > > Mark Street wrote: > > I understand. Can you explain some details/mechanism on the new 'direct > > connect' CPRS GUI. > > > > Am I assuming that the 'new way' is to make a direct connection to > > GT.M/VistA > > using a superserver connection instead of having RPCBroker listener. Did > > this grow out of limitations of RPCBroker? > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Hardhats-members mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hardhats-members > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
