ext part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20061103/187e18d3/attachment.pgp>
toad wrote:
> So when we accept a request for a peer, and it completes, we then
> allocate it another token?
Right, but this is just a first pass to get the bugs out of the
token-passing code before implementing fullest-bucket-first,
emptiest-bucket-first, etc.
Cheers,
Michael
On Fri, Nov 03, 2006 at 09:25:36AM +, Michael Rogers wrote:
> toad wrote:
> >Yes, but we will want to forward the blocks ASAP, rather than waiting
> >for everything to arrive, and we can't do that until we have the DataInsert
> >/ DataReply.
>
> Why not? If we received them before the DataInse
toad wrote:
> Yes, but we will want to forward the blocks ASAP, rather than waiting
> for everything to arrive, and we can't do that until we have the DataInsert
> / DataReply.
Why not? If we received them before the DataInsert, it must be possible
to send them before the DataInsert.
Cheers,
Mic
toad wrote:
So when we accept a request for a peer, and it completes, we then
allocate it another token?
Right, but this is just a first pass to get the bugs out of the
token-passing code before implementing fullest-bucket-first,
emptiest-bucket-first, etc.
Cheers,
Michael
_
toad wrote:
Yes, but we will want to forward the blocks ASAP, rather than waiting
for everything to arrive, and we can't do that until we have the DataInsert
/ DataReply.
Why not? If we received them before the DataInsert, it must be possible
to send them before the DataInsert.
Cheers,
Micha
