> OK, but that this has to be kept in a seperate datastore in this case, since > the closeness relation will be different from data routing.
Yes, I have created a MetadataStore. > It doesn't work. If the node keeps requesting it, chances are it will keep it > alive in the node that it has a refernce to, but not in the node that is the > "epi-center". That is indeed tricky. I'm still willing to make a first pass at implementing this and having it not work quite right because then our answer to the common question of "What if I want my information to stay in Freenet forever?" will be "You can run this program, but it doesn't work quite right. Help us fix it if you have any bright ideas." instead of "Theoretically, I guess maybe you could do that, but no one's tried." > This is not a node anyways, it is a client. A special purpose automated > client, > but a client non the less. Certainly. I mispoke when I called it a node. > > Yes, I'm going to work on the client classes so that they process trailing > > field metadata so that the www interfaces can add ContentType trivially. > > That is good. The client classes need work, unfortunately I have been afraid > to > change them now that we have Freeloader et al depending on them. Yes, I somewhat dread getting around to rewriting the clients, but it needs to be done. I think I can keep the amount of broken stuff down to acceptable levels, though, as what mainly needs to be done is breaking things up into more functions. I think maybe a new method of handling messages might be in order, though. Right now it's a big case statement and I don't really like those. I think a message handling system like the node uses would be good, replacing the node's message handler classes with new ones for the client. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
