× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David Gibbs wrote:
James H. H. Lampert wrote:
Aside from opening up a loopback TCP connection, or temporarily some
object in a library (such as the *USRQs that are so ubiquitous in socket
hand-off), does anybody know of a good way for one job to talk to another?

Data queue seems like a logical choice.

david

Queues are great for sending commands and state changes. Keyed queues
also work well for segregating data by client. A session ID, for
instance, can be used as a data queue key for returning web response
data to the middle tier. For making status values available across jobs,
user spaces work well also. They can be accessed just as if they are
local storage. Get a pointer to the space, then just offset to the value
of interest, as a data structure subfield or use a pointer offset from
the space location. I did that many moons back to sync converted S36
nep-mrt programs so only one client at a time could run the primary
program cycle. All global variables, as well as semaphore states (before
semaphores existed on the i) were stored in the user space. It worked well.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.