Re: Using TIdTCPServer

Article View: borland.public.cppbuilder.internet.socket

Article #424

Back to borland.public.cppbuilder.internet.socket Previous Next

#424

From: Remy Lebeau (TeamB)
Date: Fri, 01 Feb 2008 21:36

23 lines
2532 bytes

"Peter" <piotrtrzeciak@yahoo.com> wrote in message 
news:47a33b83$1@newsgroups.borland.com...

> So, what I did, is I added:
> AContext->Connection->Disconnect();
> at the very end of the handler to make sure that the connection is
> dropped after servicing it's content. However, I see that sometimes
> it does not cause the OnDisconnect handler to fire

When used properly, yes it will.  The rest of your OnExecute code is 
probably blocking Indy's internal notifications from reaching the server's 
internal handlers correctly so it can stop the thread accordingly.

> the server does not accept any more connections after that (almost like
> it does not yeld to the main thread).

As long as the server's MaxConnections limit has not been reached, 
TIdTCPServer can continue servicing new clients just fine while old client 
threads are still running.


Gambit

Technical Details

Message-ID: <47a390ad$1@newsgroups.borland.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!feeder3.cambrium.nl!feeder2.cambrium.nl!feed.tweaknews.nl!193.201.147.86.MISMATCH!news.astraweb.com!border1.a.newsrouter.astraweb.com!transit4.hitnews.eu!feeder.news-service.com!newsfeed.freenet.de!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

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> <47a24592@newsgroups.borland.com> <47a33b83$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> <47a24592@newsgroups.borland.com> <47a33b83$1@newsgroups.borland.com>
Subject: Re: Using TIdTCPServer
Date: Fri, 1 Feb 2008 13:36:33 -0800
Lines: 25
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: <47a390ad$1@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1201901741 207.178.157.90 (1 Feb 2008 13:35:41 -0700)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!feeder3.cambrium.nl!feeder2.cambrium.nl!feed.tweaknews.nl!193.201.147.86.MISMATCH!news.astraweb.com!border1.a.newsrouter.astraweb.com!transit4.hitnews.eu!feeder.news-service.com!newsfeed.freenet.de!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

Reply to Parent Message