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


  • Subject: RE: TCP interface problem
  • From: Tim McCarthy <TimM@xxxxxxxxxxxxxxxxxx>
  • Date: Sat, 7 Aug 1999 14:37:44 -0400

If your sockets program is expecting to always receive complete
"records" on a read then you may be asking for trouble. There is no
guarantee that a packet sent always equals a packet received. You really
need to recode the read and treat it as a stream of data rather than a
fixed length entity - and if the records are delimited by say CR/LF's
then you need to parse it out - otherwise changes to your network
hardware/topology may eventually get you.

> -----Original Message-----
> From: Rich Duzenbury [SMTP:rduz@aros.net]
> Sent: Friday, August 06, 1999 5:09 PM
> To:   midrange-l@midrange.com
> Subject:      TCP interface problem
> 
> Hello midrangers,
> 
> I have a TCP socket interface giving me fits today.  We are trying to
> move it from a V3R2 machine to a V4R3 machine with little success.
> 
> Records longer than 536 appear to be truncated.  I notice that when I
> check the TCP connection status on the new machine (Netstat, option
> 3), it happens to report 'Maximum segment size: 536'.
> 
> The old machine reports 'Maximum segment size: 1452'.
> 
> How can I convince the new system to allow the larger segment size
> (Assuming this is the real problem).
> 
> This program does not appear to use any type of SETSOCKOPT calls, btw.
> 
> Thank you.
> 
> Regards,
> Rich
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.