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? On Tuesday 21 June 2005 14:42, K.S. Bhaskar wrote: > In the case of GT.M, since there is no daemon to startup or shut down > (the first process to open a database file sets up the shared control > structures; the last one out turns off the lights), one of the benefits > of deploying a service under inet/xinetd is that when there is no > activity, everything is just shut down (i.e., no files open, no > processes active). So, it's just a little cleaner. > > In the case of VistA on GT.M specifically, the new ability to deploy a > service under inetd/xinetd allows the new direct connect CPRS GUI to be > served by a GT.M process that is started up when the connection request > comes in, rather than, for example, a pre-existing process from a pool > of processes. This is especially appropriate for deployment under > inetd/xinetd because it is a relatively long-lived connection. -- Mark Street, RHCE http://www.oswizards.com -- Key fingerprint = 3949 39E4 6317 7C3C 023E 2B1F 6FB3 06E7 D109 56C0 GPG key http://www.oswizards.com/pubkey.asc ------------------------------------------------------- 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 Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
