Article View: borland.public.cppbuilder.internet.socket
Article #5077Re: Indy9: WriteBuffer or WriteStream?
From: Remy Lebeau (TeamB)
Date: Thu, 14 Oct 2004 22:10
Date: Thu, 14 Oct 2004 22:10
13 lines
1401 bytes
1401 bytes
"Paul Machiaverna" <Paul.Machiaverna@i-stat.com> wrote in message news:416ee58c$1@newsgroups.borland.com... > What threw my off was the Indy documentation on WriteBuffer. > It has the buffer typed as a TIdBuffer The documentation is wrong. The ABuffer parameter is an untyped parameter, which is equivilent to void* in C++. Which means that the parameter can receive raw memory directly. TIdBuffer is not used at all. Gambit
Technical Details
Message-ID:
<416ef94a$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<416ecb58$1@newsgroups.borland.com> <416ed8fd$1@newsgroups.borland.com> <416ee58c$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,b4143675c7807a44,start X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <416ecb58$1@newsgroups.borland.com> <416ed8fd$1@newsgroups.borland.com> <416ee58c$1@newsgroups.borland.com> Subject: Re: Indy9: WriteBuffer or WriteStream? Date: Thu, 14 Oct 2004 15:10:39 -0700 Lines: 15 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 NNTP-Posting-Host: 68.69.17.41 Message-ID: <416ef94a$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1097791818 68.69.17.41 (14 Oct 2004 15:10:18 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!news.zanker.org!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail