But I think that the RawMessage should read the fields that relate to the transfer. Source, DataLength, and KeepAlive, which all relate to this transfer more then to the message chain need to be visible to the ConnectionHandler, which can't go looking in the message classes for them.
On Mon, 08 May 2000, Brandon wrote: > > That is is a good point. But on the other hand, streaming data will require > > changes to the protocol anyways. I think we would probably need a field like > > "StreamingData=true" or something for that, and that could override the > > absence > > of a DataLength field. > > But then we're just back to having RawMessage look for a special field. I > think it would be better if RawMessage didn't look at DataLength and the > messages that use it check for it. RawMessage should just read to the > trailing field without looking at what any of the fields are. > > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- Oskar Sandberg md98-osa at nada.kth.se #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
