Use call-out library to pass file descriptor(s) to children
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenVista/GT.M Integration |
Fix Released
|
Medium
|
jeff.apple |
Bug Description
This is an umbrella item under which bug 322031, bug 321758, and bug 323009 may fall.
Superceds bug 322036.
The use of xinetd is a problem in that its use and control is at the operating system level. There is no way to "turn off" a port from the VistA/MUMPS environment when it is defined in xinetd. However, as stated in bug 321758, starting RPC Broker from within VistA is also not working.
It is possible to obtain the file descriptor for a new connection, and to spawn off a child with this descriptor duplicated to stdout and stdin. This behavior would allow the mumps server code to work very much like Cache, where the JOBbed process inherits the parent file descriptor.
Example code has been checked into the tcpip/docs branch.
Related branches
Changed in openvista-gtm-integration: | |
assignee: | nobody → jeff-apple |
Changed in openvista-gtm-integration: | |
milestone: | none → phase-1-alpha |
Changed in openvista-gtm-integration: | |
status: | Fix Committed → Fix Released |
The common kernel routines used by some RPC Broker and HL7 routines are in ZISTCP and ZISTCPS. These two files overlap in functionality to a great degree. It may be good to know why there are two files that do largely the same thing, and why they can't be refactored into one single file.