Article View: borland.public.cppbuilder.internet.socket
Article #711Indy 9 : UDP Client help?
From: TerryC
Date: Sat, 17 Nov 2007 06:39
Date: Sat, 17 Nov 2007 06:39
19 lines
1612 bytes
1612 bytes
I created a nice, simple UDP application using the TUDP component included with BCB at one time. Apparently, this is now deprecated and Indy is the way to go. (I even looked into the NetMasters TNMUDP component, but it's about the same thing.) But Indy is a complicated jungle, created by developers who seem to revel in its complexity. The Indy documentation does nothing to change my opinion of the work. The Borland VCL is supposed to be all about RAD and a simplified development path, but Indy is running headlong in the opposite direction, IMO. It's complicated and proud of it. Enough of the rant. I need help. Is there a good EXAMPLE of the use of the Indy UDP client? Maybe I can begin to decipher what they're doing with an example. Thanks, and best regards to all.
Technical Details
Message-ID:
<473e8cb8@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-mailShow Full Headers
Complete Article Headers
X-Google-Thread: 11508e,d5288f71dfc08357,start X-Google-Attributes: gid11508e,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: "TerryC" <User@Server.Net> Newsgroups: borland.public.cppbuilder.internet.socket Subject: Indy 9 : UDP Client help? Date: Fri, 16 Nov 2007 23:39:54 -0700 Lines: 21 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 67.130.76.143 Message-ID: <473e8cb8@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1195281592 67.130.76.143 (16 Nov 2007 22:39:52 -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