Re: [freenet-dev] Read only nodes

[Lorrin Nelson]

But would anyone ever find anything on the read-only node? Say I've got 
200 items on the read-only note (ie, a couple moderate-sized websites). 
Chances are there will be no similarity between the CHKs of those items. 
(And furthermore the CHKs will bounce around wildly as the content is 
edited.) Now lets say I'm a neighboring node looking for content -- 
won't I have already learned that the read-only node never has anything 
I've ever asked it for and not keep querying it? Isn't it totally 
contrary to Freenet's fundamental design to try to route a whole slew of 
isolated CHKs to a single node?

-Lorrin

Todd Walton wrote:

On Sun, 14 Sep 2003, Edgar Friendly wrote:


pineapple <[EMAIL PROTECTED]> writes:


I was wondering if there were any plans to have the
option in Freenet for users to make their node read
only.  That is, content can only be inserted localy
and not by requests.  Some content providers may want
to make their material available permanently (or at
least as long as they desire) to freenet users, but do
not want to provide resources to Freenet (other than
the content they provide of course) for some reason.
<SNIP>

This would not work for the same reasons that every other scheme that
keeps non-requested data in your store doen't work.  The network
doesn't adapt to knowing that your node is the source of the data, and
then has everyone look there for the data.  On insert, the network
puts the data where it's going to look for it, and then looks for it
there.


Thinking about it, I figured it would work.

If a request comes from another node, check in the local datastore and 
reply based on that.  Never send the request on to another node.

But if the request comes from the local user, then send it out to the 
network like normal.

Inserts would go to where the network plans on looking for it in the 
future, like you said.  But that's not a problem, really.  There'll be 
duplication of data (something we'd like to avoid), but that's not a 
killer.  Requests for the data will go to the other node, and not our 
"read only" node, but that's not a big deal either.

The stated idea of this read only node was to ensure permanent 
availability of the data, and if the out-in-the-network node loses the 
data due to low popularity, the read only node will still have it and 
requests for it will still have a chance of finding it.

This sounds like a very clever use of Freenet, pineapple(?).  And 
certainly an inevitable one, either way, since it doesn't require any 
change in what the rest of the network does for it to work.

It would certainly be an interesting experiment, at any rate.

-todd
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl

_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl