Re: Apparent timing problem with socket communications -- 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: Apparent timing problem with socket communications
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: Tue, 9 Nov 2004 11:12:49 -0800 (PST)
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>

>    Since no one else wants to go first...
>    The part that caught my eye was the comment that
> the client "fails to receive the reply sent by the
> server."

<BIG BLUSH>
It turned out not to be a timing problem at all, but a client logic issue
that was somehow being masked by slowing down the server. Once we figured
out where to put the client-side diagnostics, it took about half a day to
fix.

--
JHHL

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.