World: r3wp

is transport a problem? :-)

well, I understand how rigid things as Uniserve works - multiplexing 
engine, various protocols/services and handlers installed .. so you 
can run http server, irc client, messenger client etc., dynamically. 
 I don't understand, how Chord would be usefull in such case for 
e.g.

... as another side has to support it too ...

so if I understand it correctly, it is good for new products, but 
not for connecting to existing infrastructures ...

if you think about a client-server architecture, of course Chord 
is not useful :-)

can you imagine IOS as non client-server = P2P architecture?

Yes, it is possible. I can actually imagine a distributed operating 
system, where the whole Internet is seen as one single computer.

dinner time, later!

... interesting - bittorent site Suprnova.org was killed, although 
I think that RIAA and other monopol orgs are crossing law here - 
IMO Suprnova did nothing illegal. I am glad it leads to anarchy ;-) 
Now Suprnova is back with Exeem, kind of P2P system for distribution 
of Torrent links and RIAA guys are finished here :-)

wonder what Exeem uses, maybe Chord too :-)

do you know XOR based Kademlia? http://citeseer.ist.psu.edu/529075.html

yes, every computer is a resource in the internet operating system...

Is there a one paragraph summary of what the above discussion is 
all about?

its all about 3k

Graham, I just asked for comments on http://www.colellachiara.com/soft/Libs/messaging.r

It's a messaging framework?

How does Chord relate to it?

My implementation to Chord is going to use it.

to = of

the discussion switched to chord because I also asked if anyone was 
interested in a function i wrote for chord, IN-INTERVAL?

do you have demonstration of how this works?

you mean messaging.r ?

actually i hope the documentation is enough; if it is not, i'll be 
happy to improve it.

some of need simple examples to get us started :(

hmm, on one computer:

handlers/insert-func 
    func [message] [
        if parse message ['ping set message date!] [
            reduce ['pong message]
        ]
    ]

listen-messages udp://:10000

on another:

send-message udp://otherhost:10000 reduce ['ping now/precise]

are you going or do you have encryption?

will be there, i've been struggling on a couple design decisions 
about it.

encryption and authentication/authorization.

as Carl says, it's so hard to make it simple... i guess i'll run 
out of time and just do something that works.

i'll then just switch to RS when they'll be out.

rugby uses 1024 bits encryption

used to say that that would take 3,000,000 years to crack ... but 
now they say governments can do it.  should switch to 2048 bits for 
espionage level encryption.

hmm, knowing Maarten, I guess he's actually using AES, which is 128 
bit; the RSA key is probably 1024.

first UNTESTED version of Chord for the brave people who want to 
have an early look inside: http://www.colellachiara.com/soft/Libs/chord.r

gonna test it tomorrow by writing a small demo script. I hope to 
find a few people wanting to partecipate in the test :) you'll need 
to be able to receive UDP packets (nat traversal and firewall support 
will come later on)

udp? Who uses unreliable protocol nowadays?

tcp/ip isn't exactly designed for end-to-end reliability either, 
Petr.

tcp just means a lot slower

1) chord is robust enough even in case of packet loss and 2) a packet 
loss problem can be solved resending packets or even using erasure 
codes or other smart tecniques

anyway the final version will work on tcp (http) when udp doesn't 
work

Gabriele, looks good! I will start testing with you next week. We 
will provide some bootstrap nodes and may get others to join as well.

We should make a /chord subdirectory of the detective site with a 
tutorial and the distro or so.

Doing good work, Gabriele...

argh, I hate job hunting.

Brian, the hunter...

Yep, that's me

i may need help testing Chord very soon, please let me know if you 
are available and can receive/send udp packets.