> Yes--quoting is gross, and that part of the spec is the most solid and
I don't like quoting either. I like the nice name=value without any restrictions. I guess it depends on how useful it would be. It seems to me that a message will expect a field to have a value of a specific type and break if the field is of some other type. I don't see messages accepting a particular field as either integer or string. They either want it be an integer or they want it to be a string. So they can just convert it themselves and yell if the conversion doesn't work. Flagging them in the protocol would only be useful if you wanted to be able to have both "94" and 94 as values, but you only want one or the other. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
