🚀 go-pugleaf

"Mike Ruskai" <BUTthannydI@DONTearthlinkLIKE.netSPAM> wrote in message 
news:tu0ss39uaq8j35if50r88eflpsf5nvs431@4ax.com...

> Which means you have to pick an arbitrary length of time you're
> willing to have the program sit doing nothing, because there's no
> function to read UP TO a number of bytes, from whatever's available,
> without blocking until that number of bytes is completely filled.

Yes, there is a way, which I mentioned in my previous reply, and below.

> As it happens, ReadFromSource() is *not* publically accessible.
> It's protected.

Sorry, I meant CheckForDataOnSource() instead:

    IOHandler->CheckForDataOnSource(10);
    IOHandler->ReadBytes(buffer, min(1024, IOHandler->InputBuffer->Size));

> One of the big problems here is documentation.  All I have to go by
> is the Indy 10.1.1 docs in BCB2007, since there's no hint of
> documentation on the Indy home page.

Then you didn't look very closely:

    http://www.indyproject.org
    Indy.Sockets (VCL) > Documentation

> From those docs, I can see that CheckForDataOnSource() calls
> ReadFromSource() internally, so is a suitable replacement for your
> suggestion.

Yes.

> It seems to work as intended, provide I use a Readable() call before hand
> as an equivalent to select().

You don't need to call Readable() or select() beforehand.  ReadFromSource() 
calls select() internally, using the timeout that you pass in.

> Well, yes.  Aside from the fact that none of the commands match those
> of FTP, the command response format is different, the data transferred
> is not the contents of a file.

TIdFTP is not limited to files only.  Any TStream can be used.


Gambit