Article View: borland.public.cppbuilder.internet.socket
Article #2369Re: TIdUDPServer (and Client)
From: Paul
Date: Mon, 29 May 2006 12:00
Date: Mon, 29 May 2006 12:00
23 lines
1564 bytes
1564 bytes
Hi, Spotted a mistake in my code, and with that fixed I've got UDP packets being received by the server and responses received back at the client. I've also now moved both the TIdUDPServer and Client components in their own thread (each), and this seems to be ok too. For now, final two questions: 1) What does the property ThreadedEvent do for the TIdUDPServer component? 2) How does the IdUDPServerStatus event get triggered? I've had an event handler registered, but I don't get any events triggered? Thanks Paul "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message news:4479fd0f$1@newsgroups.borland.com... >
Technical Details
Message-ID:
<447ae24c$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news4.google.com!news2.volia.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<44796d7e$1@newsgroups.borland.com> <4479fd0f$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,826a7ca2cbe06100 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Paul" <plmacca@clara.co.uk> Newsgroups: borland.public.cppbuilder.internet.socket References: <44796d7e$1@newsgroups.borland.com> <4479fd0f$1@newsgroups.borland.com> Subject: Re: TIdUDPServer (and Client) Date: Mon, 29 May 2006 13:00:33 +0100 Lines: 25 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 86.132.252.247 Message-ID: <447ae24c$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1148904012 86.132.252.247 (29 May 2006 05:00:12 -0700) Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news4.google.com!news2.volia.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail