Re: Odd Sockets Problem... -- MIDRANGE-L

× 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: Odd Sockets Problem...
From: "Brad Stone" <brad@xxxxxxxxxxxx>
Date: Wed, 11 Aug 2004 07:07:00 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Wed, 11 Aug 2004 02:04:34 -0500 (CDT)
 Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote:
> 
> You must write your applications so that they understand
> this.  They
> should call the recv() or read() API in a loop until they
> get all of the
> data that they intend to receive.

That's the problem.  how much to receive is an unknown.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Odd Sockets Problem... , John Ross

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.