Async file I/O

sergey -

I think that you will find that if you use API file functions in VB, you
will gain little to no performance benefit, plus the disadvantage that your
code will be more obscure.

--

------------
Mark Alexander Bertenshaw
Programmer/Analyst
Prime Response
Brentford
UK
"sergey" <skats@newworldsys.com> wrote in message
news:38d2cad4$1@news.dev-archive.com...
>
> Hi.
> I'm developing a component that handles file I/O in my app, and before
jumping
> into development I'm wondering how hard is it to do that using win APIs?
> And have anyone done it before? Maybe you guys know of any third party
cheap
> component that will handle that kind of functionality?
>
> Thanks
> Sergey

"sergey" <skats@newworldsys.com> wrote:
>
>Hi.
>I'm developing a component that handles file I/O in my app, and before jumping
>into development I'm wondering how hard is it to do that using win APIs?
>And have anyone done it before? Maybe you guys know of any third party cheap
>component that will handle that kind of functionality?
>
>Thanks
>Sergey

Like the other post says, it is no big performance enhancemnt.
If you still want to try, just "to know how it is done!", then
there is a CopyFileEx Api, to which you can specify a Callback function (
the aim being the call back fn will do some kind of UI updation may be!),
which will be called after each block is copied, and using which you can
also pause & restart after some time, or cancel & quit
Take a look at CopyFileEx fn on MSDN

Thanks for responses guys.
On that note I think that async files i/o would be an overkill in my app.
The files are not that big anyway.

Sergey.

"Ravi Kiran" <ravi_kiran@yahoo.com> wrote:
>
>"sergey" <skats@newworldsys.com> wrote:
>>
>>Hi.
>>I'm developing a component that handles file I/O in my app, and before
jumping
>>into development I'm wondering how hard is it to do that using win APIs?
>>And have anyone done it before? Maybe you guys know of any third party
cheap
>>component that will handle that kind of functionality?
>>
>>Thanks
>>Sergey
>
>Like the other post says, it is no big performance enhancemnt.
>If you still want to try, just "to know how it is done!", then
>there is a CopyFileEx Api, to which you can specify a Callback function
(
>the aim being the call back fn will do some kind of UI updation may be!),
>which will be called after each block is copied, and using which you can
>also pause & restart after some time, or cancel & quit
>Take a look at CopyFileEx fn on MSDN