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,fed2e7871ca258cd X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-12-19 10:16:06 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!nntp.cs.ubc.ca!nntp-relay.ihug.net!ihug.co.nz!telocity-west!TELOCITY!sn-xit-03!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "Matthew Heaney" Newsgroups: comp.lang.ada Subject: Re: Server - tasking and long lived connections Date: Wed, 19 Dec 2001 13:20:07 -0500 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Complaints-To: newsabuse@supernews.com Xref: archiver1.google.com comp.lang.ada:18103 Date: 2001-12-19T13:20:07-05:00 List-Id: "Eric Merritt" wrote in message news:mailman.1008382022.25904.comp.lang.ada@ada.eu.org... > Anyway, I am just looking for some one to either point > me in a different direction or confirm my current > approach (one thread per connection). One thread per connection cannot possibly scale well. It is the *wrong* way to implement a server. Our RTSP video server uses WinNT I/O completion ports, so that a small number of tasks (threads) can service hundreds (or even thousands) of client connections.