On Wed, 4 Apr 2001, Brandon wrote:
> Oh, and BTW, please just ignore me if anything I said was totally
> incoherent. I am immensely sleepy and should not be allowed to post things
> in this state. Last time I tried it was very embarassing. I can only hope
> for the best.
Here's my sleepy gripe. Say your client gets a request for
"freenet:KSK at wumpus//dweezil.tiff". If Client doesn't handle metadata
internally, you'll end up doing something like:
request "freenet:KSK at wumpus"
if it's a control document
look up "dweezil.tiff" (with std utility function)
if it's a redirect
get target with std function
start over
if it's a splitfile
stream splitfile with std function
That's really annoying compared to:
add desired metadata handlers
request the URI
And what happens when new kinds of metadata are added, and you want your
client to automatically support them? With an internal metadata handler
system, you could do something like:
c.addAllHandlers();
But with an external handler system, your only choice would be to use
SimplifiedClient, and suffer within the constraints of the simplified API.
--
Satan, oscillate my metallic sonatas!
Mark Roberts | mjr at statesmean.com
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
