[OpenDHT-Users] inconsistencies

[Sean Rhea]

Hmm.  Works for me:

$ ./put.py key1 value1
Success
$ ./get.py key1
value1

What key were you using?  Do you still see the problem?

OpenDHT stores each key on several nodes, so you shouldn't need to use
multiple keys per value.  Submitting each get through several
gateways, on the other hand, does improve latency a lot.  See our
WORLDS paper for details:

  http://srhea.net/papers/opendht-worlds05.pdf

Sean



On Dec 13, 2007 7:33 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
> The latest interesting aspect seems to be
> run put key1 value1
>
> then run
> get key1
> and it will either (I believe) just give up on the connection, so the
> python version tries over and over again, or return 'blank'
> but only for certain keys
> guess it reiterates the importance of using multiple keys for the same value.
> take care.
> -Roger
>
> Rogers-little-PowerBook:python roger$ python put.py -g
> http://opendht.nyuld.net:5851 key1 value1 -s secret
> Success
> Rogers-little-PowerBook:python roger$ python get.py -g
> http://opendht.nyuld.net:5851 key1
> Rogers-little-PowerBook:python roger$
>
> Note this may be caused by me running 'put key1' about 100 times in a
> row, but I wouldn't anticipate that as having caused any problems.
> _______________________________________________
> OpenDHT-Users mailing list
> OpenDHT-Users at opendht.org
> http://opendht.org/cgi-bin/mailman/listinfo/opendht-users
>



-- 
"Humanity has advanced, when it has advanced, not because it has been
sober, responsible, and cautious, but because it has been playful,
rebellious, and immature." -- Tom Robbins