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,3190aba277f0ce3e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-15 23:33:04 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.ems.psu.edu!news.cse.psu.edu!uwm.edu!newsfeed.cs.wisc.edu!newshub.sdsu.edu!west.cox.net!cox.net!nntp2.aus1.giganews.com!nntp.giganews.com!nntp3.aus1.giganews.com!bin3.nnrp.aus1.giganews.com.POSTED!news.clear.net.nz From: Craig Carey Newsgroups: comp.lang.ada Subject: Re: Question on Client - Server communication Message-ID: References: X-Newsreader: Forte Agent 1.9/32.560 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Organization: Customer of Mercury Telecommunications Ltd Cache-Post-Path: drone3-svc-skyt.qsi.net.nz!unknown@tnt1-18.quicksilver.net.nz X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/) X-Original-NNTP-Posting-Host: drone3-svc-skyt.qsi.net.nz X-Original-Trace: 16 Jul 2002 18:32:44 +1200, drone3-svc-skyt.qsi.net.nz NNTP-Posting-Date: Tue, 16 Jul 2002 01:32:47 CDT X-Trace: sv3-FkdH11vBX2rkjZNHPi4jplYhvQZE9eZ2jzaXeP4kVyEgKkhTHaQhSEwxmn10034hYPAUdzHDBPXLaZK!mVusYzPPVW5obcQZBWIzO5XPsjFRegEDEmsM2mAr1zGyvaQm6ISiMQMHw+ouqOGX7xu8BhVOT3nm!wvf8xQ== X-Complaints-To: abuse@GigaNews.Com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly Date: Tue, 16 Jul 2002 06:32:47 GMT Xref: archiver1.google.com comp.lang.ada:27131 Date: 2002-07-16T06:32:47+00:00 List-Id: On Sun, 07 Jul 2002 02:37:43 GMT, Caffeine Junky wrote: >On Sat, 06 Jul 2002 15:55:11 -0400, Preben Randhol wrote: > >> Caffeine Junky wrote on 06/07/2002 (03:12) : >>> Use port "forwarding". Very simple. >>> >>> The server designates a standard port. The application connects to the >>> server on that port. The server then tells the application to switch >>> to port number X and opens a connection on that port. This leaves the It is better to not switch to a different port numbers. >>> original port open to recieve more app requests. There are alot of It remains open anyway. There can be one call to "bind()" where the port number is given, and then many calls for to accept() for each TCP thread. Port forwarding does not have switching to port numbers. To have a single listening port number, can mean that code to strip off headers is needed. I have free source code that removes HTTP/1.0 headers like a client or a webserver does: it is simple code that would need a bit of rewriting: http://www.ijs.co.nz/code/ada95_strings_http_hdrs.zip (That file contains a usable experimental replacement for Ada's Unbounded Strings package. It is an improvement.) ... >Well...depends on what your doing with the tasks. If the tasks are >generating alot of traffic, it might simplify things to tack on an >additional port per Y number of tasks. i.e. Open another port for every >10 tasks. This way the timing issues should be less troublesome. ... Caffeine might wish that the word "timing" was replaced with: "ordering". Also, adding unnecessary complexity does not simplify. It sounds like an interesting project (now that I saw another message to CLA saying that Ada tasking and XFree86 (GtkAda too?) are somehow incompatible). I didn't catch all the details.