> What metadata do you need to implement? The storable fields ARE the metadata, > any other metadata should be in the trailing, not in the message, like we > decided.
Right, I want to make the clients read the metadata stored in the trailing field and I want to use the same code that RawMessage uses to read fields to read the information in the trailing field because while the trailing field could be in any format and the nodes wouldn't care, I think the clients should all use standard field formatting. > Nodes need to be able to talk to one another. We should not have it so they > can't. But it is inevitable that people will want to add different message encodings and that not all nodes will be mutually interoperable over all encodings. For instance, there is already the desire to encode Freenet streams with SSL so as to mask that they are Freenet streams. How can we add this capability without supporting multiple protocols and specifying the protocol explicitly in the address? > I think we should spend more effort on forwards compatibility for the versions > of the protocol that will actually be used. True. I was just mentioning that because it's a nice and useful side effect of implementing multiple message protocols. The reason I really want it is for forward compatibility and because my node should be able to speak to both normal Freenet connections and SSL connections. It should be able to pretend to be a webserver, FTP server, etc. and still talk to normal Freenet nodes and we need some way to tell a node if the thing it's connecting to is going to act like a normal Freenet node, pretend to be a webserver, etc.. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
