|
David Given that the processes will be on separate systems have you thought about MQ ? What you are describing sounds like a good scenario for MQ rather than trying to deal with all the process etc issues yourself. regards Evan Harris >Folks: > >We've got a project brewing where we have to communicate between java & rpg. >The java program is not necessarily going to be running on the 400 (in fact, >probably won't be). > >We're planning on using the Toolkit (probably JTOpen, but not 100% sure yet) >to implement remote data queue listeners. > >I'm curious if anyone knows of a "Recommended" way of using data queues for >inter system communication? > >Also, does anyone know of a way to handle "Process Death" on either side of >the connection? If I were using TCP, I would just look for a closed socket. >With a dataqueue, the potential exists for the remote process (the one that >feeds the data queue) to die and the local process (the one that eats the >data queue) to just wait forever. > >Thanks! > >david +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
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.