Article View: borland.public.cppbuilder.internet.socket
Article #413Re: Using TIdTCPServer
From: Remy Lebeau (TeamB)
Date: Thu, 31 Jan 2008 20:12
Date: Thu, 31 Jan 2008 20:12
29 lines
2327 bytes
2327 bytes
"Peter" <piotrtrzeciak@yahoo.com> wrote in message news:47a2265f$1@newsgroups.borland.com... > So... here is an interesting outcome. For future reference, please trim your replies. > I execute the service, attach it to CodeGear debugger, send some > data, and it works, yet the same thing refuses to "service" more than > one socket connection, when executed normally (without the debugger). Then please show ALL of your code, or at least make a minimal test project that reproduces the same problem. There has to be something in your code that is serializing/deadlocking the threads. By itself, TIdTCPServer can service multiple clients at the same time without problem. > What, if any, maintenance must be performed on the instance of the > IIdTCPServer? None by you. It is all handled internally by Indy for you. > Are there any special properties that must be set, in order to run the > code concurrently? No. Gambit
Technical Details
Message-ID:
<47a22b93$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<478e1c34$1@newsgroups.borland.com> <478e4760@newsgroups.borland.com> <4798a5e1$1@newsgroups.borland.com> <4798cf30$1@newsgroups.borland.com> <4798db8f$1@newsgroups.borland.com> <4798ef34$2@newsgroups.borland.com> <479e2c75$1@newsgroups.borland.com> <479e382e$1@newsgroups.borland.com> <479f4835$1@newsgroups.borland.com> <479f51f8$1@newsgroups.borland.com> <479f68b1$1@newsgroups.borland.com> <479f7070$1@newsgroups.borland.com> <479f9ae1$1@newsgroups.borland.com> <47a2265f$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,452e664b18b0b56c X-Google-Attributes: gid11508e,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <478e1c34$1@newsgroups.borland.com> <478e4760@newsgroups.borland.com> <4798a5e1$1@newsgroups.borland.com> <4798cf30$1@newsgroups.borland.com> <4798db8f$1@newsgroups.borland.com> <4798ef34$2@newsgroups.borland.com> <479e2c75$1@newsgroups.borland.com> <479e382e$1@newsgroups.borland.com> <479f4835$1@newsgroups.borland.com> <479f51f8$1@newsgroups.borland.com> <479f68b1$1@newsgroups.borland.com> <479f7070$1@newsgroups.borland.com> <479f9ae1$1@newsgroups.borland.com> <47a2265f$1@newsgroups.borland.com> Subject: Re: Using TIdTCPServer Date: Thu, 31 Jan 2008 12:12:48 -0800 Lines: 31 Organization: Lebeau Software X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 NNTP-Posting-Host: 207.178.157.90 Message-ID: <47a22b93$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1201810323 207.178.157.90 (31 Jan 2008 12:12:03 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail