From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d0728b52f51f685e X-Google-Attributes: gid103376,public Path: controlnews3.google.com!news1.google.com!news.glorb.com!cyclone1.gnilink.net!gnilink.net!wns13feed!worldnet.att.net!attbi_s02.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: copy constructor for sockets References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 24.6.132.82 X-Complaints-To: abuse@comcast.net X-Trace: attbi_s02 1085467033 24.6.132.82 (Tue, 25 May 2004 06:37:13 GMT) NNTP-Posting-Date: Tue, 25 May 2004 06:37:13 GMT Organization: Comcast Online Date: Tue, 25 May 2004 06:37:13 GMT Xref: controlnews3.google.com comp.lang.ada:813 Date: 2004-05-25T06:37:13+00:00 List-Id: >> One more thing: if the server does the Get_Line, that suggests >> there's only one Get_Line per accept(), ie, no persistent >> connections. > >I don't see that, so long as the server hands on the connected socket? When a Get_Handler task is done with the Get, does it do a Get_Line to see if the socket is persistent, and if so, what is the next request? If the server does the Get_Line that determines whether the next request is a Get or a Post, how does it handle the next request on a persistent connection? The server must be coded to wait, not simply for an accept() to unblock, but for either an accept() unblock OR a worker task finishing and handing back the (still potentially live) socket.