-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Only application that want to _use_ the fields, not merely pass > them from here to there. If you want to manipulate a field in a > Freenet messages, you had better know why. And that reason is > encoded in its name. That's fundamental to the semantic content > of the protocol. HopsToLive and Depth are both integers, and if > you want to encode them that way to pass them along, fine. But if > you intend to modify, delete, or add one of them, you need to know > why, and that information exists in the name.
Oh, that I totally agree with. Thats why I also think having complex types like date is unnecessary. Represent it as an integer, and let the application logic deal with it. I think that there is an appropriate balance between "Let the application have to deal with everything" and "Have a type for everything". -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5IElLpXyM95IyRhURAtKgAJ9wtuOOSRPVslCS5vsO0SwJs6n2lACfdFiR YakFRHwitQUVvrdwX3S5cn8= =q8kS -----END PGP SIGNATURE----- _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
