[Grub-dev] tiered client, other thoughts...

[Eriam Schaffter]

>> Also the individual URI is a nice unit to divide work in a multi-
>> threaded client, which would then place the burden of re-ordering
>> the results on the client side just so the hash can match...  I
>> don't know, maybe I just need to be convinced some more on this.
>
> So, the client can still process them threaded, as long as it re-
> assembles them in the resulting arc... it'll be more work to pull it
> apart and reassemble in the right order so it might not be worth it.
> The best alternative that I highly suggest, is just getting multiple
> workunits in parallel, fetch 10, 20, or even 50 at once, should be
> fine :)
>

I'm working on a POE powered client (command line for now). It should be
out before this week end. I just need some time to tweak a few things.

For your information POE is a multi-tasking framework (cooperative
multi-tasking) built in Perl with non-blocking IO.

>From what I understand the results order is important ? Or are you talking
about data chunks order ?

Actually even if the URL results is ordered I thinks it's not a big deal
and the NBIO is probably worth doing it anyway.

Thanks

Eriam