> To that extent, fields in memory should be in their native formats. The > Freenet protocol as is states that these fields must be converted to > strings, then back to values (your opinion varries only where this action > takes place). Allowing non/string values makes the writing of more > efficient protcols far more easy. To spec all data in freenet as > "Strings" is shortsighted and lazy. They simply aren't.
You entirely misunderstand my argument. Of course I don't give a damn what's in memory. Oskar was asking about putting as standard quoting mechanism into the header field text in messages, and that IS a protocol issue. I am arguing that this is a counterproductive complication to the spec, and what he wants to do with the implemtntation can be done without it. -- 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
