:Proposal:
:
: - allow multiple (an arbitrary amount of) objects with the same key
: - the clients are responsible for recognizing and selecting appropriate
: objects to present to the user based on the content
: - no updates to objects are possible
Yeah, multi-sourced and multi-destined links are what I think are a good
way to go too.
As for who sorts out which one to send, some of this can be done by
metadata in the request, and if the request doesn't specify enough data to
distinguish between two documents, the request could return only the
metadata itself from each of them, allowing the requestor to re-request
with more specific metadata.
But i'm not so sure that "no updates" is necessary. Documents digitally
signed by the author should probably be allowed to be UnRequested (if I'm
not abusing that term) by the same.
-jake
IP Multicast/HTTP Cloaking/Linux Client QA Dude
Core Technologies, Media Systems, RealNetworks
<disclaimer> My employer disavows all knowledge of stuff </disclaimer>
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
