From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 330 invoked by alias); 21 Oct 2003 17:49:15 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 322 invoked from network); 21 Oct 2003 17:49:15 -0000 Received: from unknown (HELO web14201.mail.yahoo.com) (216.136.172.143) by sources.redhat.com with SMTP; 21 Oct 2003 17:49:15 -0000 Message-ID: <20031021174914.12567.qmail@web14201.mail.yahoo.com> Received: from [208.248.82.254] by web14201.mail.yahoo.com via HTTP; Tue, 21 Oct 2003 10:49:14 PDT Date: Tue, 21 Oct 2003 17:49:00 -0000 From: Matt Jerdonek To: David Vrabel , Discussion eCos In-Reply-To: <3F95597F.4010505@arcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS] TCP Transactions X-SW-Source: 2003-10/txt/msg00376.txt.bz2 I'd love to use UDP, but the project requirements specify TCP. Does anyone know how other systems handle the TIME_WAIT situation? Thanks, -- Matt --- David Vrabel wrote: > Matt Jerdonek wrote: > > > > I'm developing an application that sends small > > transactions via TCP. The basic flow is 1) Bring > up > > the connection 2) Send request 3) Get response 4) > > Bring down the connection. Simple enough ... > > Have you considered using UDP and manually handling > any required retries? > > David Vrabel > -- > David Vrabel, Design Engineer __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss