Jerome Flesch schrieb: > I commited a patch into the node to make it possible to ask for expected data > types with FCP. > See http://wiki.freenetproject.org/FCP2p0GetConfig , > http://wiki.freenetproject.org/FCP2p0ConfigData . > > I hope it will help you (anyway it will help me :) > > For periods, I can't make the data type more specific than "string" at the > moment, sorrry. > > Currently, I'm wondering if it would also be a good idea to convert all the > values into basic units (-> in bytes) and let the client apps displays it in > a more user-friendly way ? (I'm not really sure how the client would handle > values like '1025' ...) >
Probably a good idea. This would separate processing logic from representation logic. Different clients may have different needs how to present 1K to the user. This is nothing the node should care about. Same goes for time intervals. But it may break existing clients. > In the wiki or in the sources? For the sources a (parsable) header file > containing > all message / field / type decls would put a smile on my face. > > > I was thinking in FCP (and so in the wiki :) > I'm not sure to see what you mean an "parsable" header file (or at least, I'm > not sure where you want to put this header in the source ?) > On second thought, extensive documentation is better. Would be nice to have one single file in freenets sources you can parse for consts and the like but this is really of minor importance. Juergen ...almost forgot. in node/PeerManager.java I can see all the peer node status consts defined. >> public static final int PEER_NODE_STATUS_CONNECTED = 1; In the Peer message this translates to 'CONNECTED'. Do you have a pointer where this is done?
