On Thu, 11 May 2000, Lee Daniel Crocker wrote: > > > However, I'm okay with dropping unknown fields in the small number of > > > cases where a node reads a message via an untyped protocol and then writes > > > it using a typed protocol. > > > > I don't understand this. Are you talking about a gateway? What typed > > protocol? > > I'm not sure what he's talking about either. And handling unknown fields > is also rigorously defined in the spec already. And as I've said before, > Freenet protocol IS typed: field names are types.
What you are missing, and what Brandon pointed out (I really hope this is in the spec) is that the node has to be able to handle FieldNames that it does not directly recognize. This important for forward compatibility - a new field could become effective even if 100% of the nodes don't recognize it, as long as they pass it on. For the fields which I know what to expect from the current version is not a problem. The problem is that the transport characteristics (like the how values are encoded) leak through to the rest of the node on fields that are not directly recognized. > -- > Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lee/> > "All inventions or works of authorship original to me, herein and past, > are placed irrevocably in the public domain, and may be used or modified > for any purpose, without permission, attribution, or notification."--LDC > > > _______________________________________________ > 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
