Matthew Toseland wrote: > On Wednesday 26 August 2009 01:38:29 Daniel Cheng wrote: > >> On Tue, Aug 25, 2009 at 11:44 PM, Ian Clarke<ian at locut.us> wrote: >> >>> On Tue, Aug 25, 2009 at 8:51 AM, Matthew >>> Toseland<toad at amphibian.dyndns.org> wrote: >>> >>>>> It's not a joke but I admit I misunderstood the specification. I was >>>>> wondering how to detect the end of a AllData reply and I thought there >>>>> would be something such as "EndMessage". >>>>> >>>> No, it ends with the word "Data" on a line by itself and is followed by >>>> the data. >>>> >>> To clarify, the plaintext part of the message ends with "Data" on a >>> line by itself. >>> >>> It is followed by the raw data. It is not necessary to specify when >>> the raw data ends since its length is provided in the plaintext part >>> of the message. >>> >> The current implementation would be confused if you do this: >> >> ClientPut<CR> >> blbarlbalr=...<CR> >> blbarlbalr=...<CR> >> DataLength=1<CR> >> Data<CR> >> <LF> >> >> This should insert a single byte file with <LF>, but it would get confused. >> > > So the problem is we don't assume the client consistently uses the same > linefeed marker? File a bug. >
Err... this problem started after I've misread the spec. Easy solution is to parse the DataLength value and just read the number of bytes as the DataLength value? > ------------------------------------------------------------------------ > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
