[Edonkey-java-devel] RE: Out of syncness

[Robin <ke...@if...>]

> > > [snip]
> >
> > Huh, as I said, whatever it receives, if the
> CLC respects
> > his own protocol (HEADER-SIZE-MSGID-PAYLOAD),
> there should
> > be no "out of sync" situation. May I suspect
> the CLC not to respect
> > this simple protocol ? the message: Size is not
> match with actual
> > read: MessageID: 199 size: 123 actual read: 108
> > seems to confirm the fact, isn't it ?
>
> >No, the CLC respects this protocol. The CLC will
> always produce packets
> >where a header that says 'size=X' is followed by
> X bytes of data.
> Always :->)
>
> If the packets that the core sends out to the GUI
> are always correct
> according to the 2 bytes for length, then there
> shouldn't ever be an out
> of sync problem if the EJC is properly coded.

Yes there is, in fact, the problem is in the end of the
dispatchMessage switch, the patch sent by Tim was good but
not enough to solve the problems. At the end of the switch,
if the packet is not "processed", it flush the packet, but
if the packet is "processed", it displays a message "size
mismatch", but doesn't flush, I continue working on it,
keeping the first Tim Patch.

> I just got back from Cornell, so I've got to
> finish unpacking and such,
> but since I don't start work for another week
> I'll futz around with the
> packet handling code next week.

I hope it will be fixed at this time, but the more we'll be,
the better it will be.

See you,
Robin