|
The technique that you're discussing (using multiple displays in a single program) really isn't a good way to write a TALK utility. For a talk utility, you'd be better off using either data queues (because they're simple) or sockets (because they allow you to communicate across more types of networks, and with more different types of computers) I'd be happy to explain some of this, and show you some code samples, but we should move this to RPG400-L first. I don't feel comfortable posting RPG code samples on MIDRANGE-L. On Mon, 20 Oct 2003, Booth Martin wrote: > "Care to share?" Sure, why not, but no laughing, ok? I would like to > develop a TALK utility. Reaching another user for a casual question is not > graceful. Obviously the phone or Instant Messenger will always be a better > method, but sometimes you just need to ask a quick question and SNDBRKMSG is > not very graceful. > > My thought is that a single subfile of the typed comments of the user(s) > connected would be common to all screens, and would appear to be a simple > solution to the problem of sending messages back & forth between users. My > other thought now that I've seen Scott's comments is that the utility could > easily include more than two users. > > Whether this utility is useful or not is moot. My interest is in the > problem itself. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.