On Tue, 27 Feb 2001, Adam Langley wrote: > The node shouldn't handle Metadata. People can put any library > wrapppers around FCP they like. If clients want high-level access, use > the library. If not - don't. I don't even think that fproxy should be > tightly in the node. There should be a FCP fproxy which handles > Metadata for the browsers, and the metadata handling can be split off > it other people want it. >
hehe, back to the metadata arguments... How about an optional redirect handler field like this: ClientGet URI=KSK at test.html HopsToLive=10 RedirectHandler=HTTPRedirect EndMessage and dynamically load the HTTPRedirect class to process the metadata. The swarm/MPC style redirect may be too connection intensive for FCP (as the MSK/MapHandler currently is for fproxy). It's true that localhost connections are cheap in whiterose, but they aren't as cheap in Fred where more connections mean more threads. _______________________________________________ Devl mailing list Devl at freenetproject.org http://www.uprizer.com/mailman/listinfo/devl
