[Cxtable-devel] A longer reply to "p2p, the next generation"

[Williams, D. <DAV...@ca...>]

Borne-

OK.... 

I am assuming, then, that a Server is a persistent thing...?  It is always available, or this is incorrect?  Either way.... I would make this akin to my mind to the current Registry server process (which also handles relay communications when direct, and peer-enable, both fail..)..  It could handle many other processes as well..but at this time, does only those two...  

The Service..  These services, run, then, on the Server, and cache to their backup?  Or did I miss this point?  

The Client...  This client has a list of services it can connect to... This is definitely a planned but lacking feature for cxtable.  Cxtable assumes that everyone connected to it wishes to connect to one another... the persistent connection between each peer eventually allows the runner of the Registry server to pull down that server process, and have a set of X people connected with one another, but closed off to the rest of the 'network'..

Service Discovery...
URL-scanning is good.  I personally like the PHP-piece, as the act of registering a server for the availability of use to clients can be done with a URL scan as well..  Either way...this basic idea does seem to be in line with how I do it (or hope I do)

Persistence...
I have given no thought to persistence.  These ideas seem valuable, for sure..

Security/Service Ownership..
Contrary to what the code would tell you.. I have given thought to security...  Relating to public keys...  these keys generally can be published anywhere (hence their name) and could be provided along with the peers other information (IP, port, etc..), unless your intention is to route all communicae through a Server, and then, if course, only the server would need to know it...  

---------------------------------------

Each of the above points has merit with relation to the project I currently have, and at the same time..  I pause... as there are one or two points that I am unsure of..

Is the goal of the p2p to have places that relay which are persistent?  Because this vision does give way to a couple of weaknesses...  One of these weaknesses is that if they can pin down where you are, and where you'll always be...  Then they can shut you down....  The other is the need for a certain type of cash-flow to support the persistent servers... 

However, as I continue to read through this, I am of the belief that the servers you speak of could be EITHER a persistent server in the traditional sense, OR a peer-type server that is fairly transient...  

Change is not a bad thing...and this is definitely the type of thing I set myself up for by inviting new creative blood to come look, to come help....

I think that the changes you propose are worth pursuing.  I think that certain services, under the new modified vision, would allow for the "Intranet over the internet" concept to remain, and at the same time widen the vision to incorporate many other takes..

This is all assuming that you haven't decided to ditch me for Grapevine ;-)

~Dave


David Scott Williams
Computer Associates
Marketing Representative-Sales Call Center
One Computer Associates Plaza 
Islandia, New York  11749
tel: +1 800-243-9462 ext. 73431
tel: +1 631-342-3431 (Direct)
fax: +1 631-342-5734
wi...@ca...