Article View: borland.public.cppbuilder.internet.socket
Article #5025Re: Indy AThread Question
From: James
Date: Wed, 20 Oct 2004 20:20
Date: Wed, 20 Oct 2004 20:20
33 lines
1920 bytes
1920 bytes
Right, I understand how to serialise access to the AThread from my secondary thread using Critical Sections, but how could I implement this in the OnExecute event? Thanks for your time (and patience!!!), - James "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:417351b7$1@newsgroups.borland.com... > > "James" <jb9@btinternet.com> wrote in message > news:4172eeb4$1@newsgroups.borland.com... > >> So a better way would perhaps be to store the OnExecute thread's >> thread id, and then send the OnExecute thread a 'thread message' >> (from my secondary thread) which it could pick up and send using >> AThread? > > There is no reason why you cannot store the AThread pointer itself, just > as > long as you are protecting it, that is all. I would not recommend the > thread message approach because that does not well suit Indy's server > design > in general. > > > Gambit > >
Technical Details
Message-ID:
<4176c89d$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.media.kyoto-u.ac.jp!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<417256cf$1@newsgroups.borland.com> <4172b877$1@newsgroups.borland.com> <4172eeb4$1@newsgroups.borland.com> <417351b7$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,67c4133e59baab76 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "James" <jb9@btinternet.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <417256cf$1@newsgroups.borland.com> <4172b877$1@newsgroups.borland.com> <4172eeb4$1@newsgroups.borland.com> <417351b7$1@newsgroups.borland.com> Subject: Re: Indy AThread Question Date: Wed, 20 Oct 2004 21:20:46 +0100 Lines: 35 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 81.155.214.249 Message-ID: <4176c89d$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1098303645 81.155.214.249 (20 Oct 2004 13:20:45 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.media.kyoto-u.ac.jp!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail