Article View: borland.public.cppbuilder.internet.socket
Article #2033Re: Indy 9 TIdFTP Client - when is a Put() finished?
From: Lesley Anne
Date: Wed, 23 Aug 2006 21:01
Date: Wed, 23 Aug 2006 21:01
18 lines
1856 bytes
1856 bytes
> Indy is not an event-driven library. You don't need to use > the OnAfterGet event. Like everything else in Indy, Get() > and Put() are blocking functions. They do not exit until > their work is finished. > > > How can I tell when the transfer is complete? > > When Put() exits. Oh, good. That makes it easier than I thought. (Sorry if it was a dumb question. I haven't worked with the Indy library very much. So far I'm liking it, but I'm not really used to it yet. It organizes things a lot differently than the TurboPower library that I've worked with before.) So if the current function is going to remain at this call throughout the file transfer, does that mean it's designed to be put into its own thread, or does Put() contain provisions for making sure that the Windows Message queue will keep being processed as necessary?
Technical Details
Message-ID:
<44ecc221$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<44ec9e0a@newsgroups.borland.com> <44ecb32d$3@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,14159208397bbfa4 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Lesley Anne" <mspfila-ng@yahoo.com> Newsgroups: borland.public.cppbuilder.internet.socket References: <44ec9e0a@newsgroups.borland.com> <44ecb32d$3@newsgroups.borland.com> Subject: Re: Indy 9 TIdFTP Client - when is a Put() finished? Date: Wed, 23 Aug 2006 17:01:14 -0400 Lines: 20 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.2962 X-RFC2646: Format=Flowed; Original NNTP-Posting-Host: 144.160.5.25 Message-ID: <44ecc221$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1156366881 144.160.5.25 (23 Aug 2006 14:01:21 -0700) Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail