|
I forgot to mention, I'd go with the TCP method. And use the lock method previously described to handle any problems caused broken connections or standby mode issues. But TCP seems easiest, to me atleast. Tom | -----Original Message----- | From: Andy Holmer [mailto:aholmer@xxxxxxxxxx] | Sent: Friday, September 19, 2003 12:58 | To: rpg400-l@xxxxxxxxxxxx | Subject: Calling for socket type opinions... | | | At the risk of starting an uproar - I have a socket opinion | question. | | | | I am writing an application for a barcode handheld that | will communicate | back to a 400 running a socket server program. The | handheld will be RF | and there may be a couple hundred talking to an RPG socket server | program at any one time. I will be writing the server | first, as soon as | the protocol is decided. | | | | The question is: Would it be better to use the TCP | protocol and have a | socket listen() and create more descriptors, or would UDP be more | appropriate? My TCP hang up is that the connections may be | broken by | walking into an area of no RF coverage or the handheld going into | standby mode. My UDP hang up is, well, it's UDP. | | | | Your thoughts? | | | | Andy Holmer | | 1095 Nimitzview Drive | | Suite 403 | | Cincinnati, OH 45230 | | (513) 232-9100 | | f-(513) 232-9249 | | | | | _______________________________________________ | This is the RPG programming on the AS400 / iSeries | (RPG400-L) mailing list | To post a message email: RPG400-L@xxxxxxxxxxxx | To subscribe, unsubscribe, or change list options, | visit: http://lists.midrange.com/mailman/listinfo/rpg400-l | or email: RPG400-L-request@xxxxxxxxxxxx | Before posting, please take a moment to review the archives | at http://archive.midrange.com/rpg400-l. |
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.