× 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.


  1.  Home
  2. RPG400-L
  3. September 2003

Re: Calling for socket type opinions...

Andy Holmer wrote: 
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.

I would stick with TCP precisely because you have possible network outages. As I understand things, UDP is used not when the network is unreliable, but when speed is most important. TCP is more fault tolerant and therefor a better match for an unreliable network.

James Rich


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.