FROM : Roarke Lynch
DATE : Mon Jan 27 04:12:54 2003
On Sunday, January 26, 2003, at 11:55 AM, Jaime Magiera wrote:
> I'm a little late on this thread (been working hard)...
>
> In true Peer-to-Peer, there isn't an intermediary server to route the
> requests. Each app is both client and server, who can talk to each
> other directly. Many so-called P2P apps aren't really, since they use
> a routing server. You knock out the main server, you loose the ability
> to communicate.
>
> I'm writing as P2P app right now. It's called ThoughtConduit. It
> really wasn't to difficult -- You write some server code to receive
> data, you write some of code to send data. Right now, TC data is
> passed as SOAP messages.
>
> * We are also creating a routing app in WebObjects that can offer many
> of the desktop features to users logged in at the site. This is just
> to support those who would sacrifice true P2P for the convenience of
> doing transactions through the browser.
>
> Jaime
It might not be that difficult, but I'm looking for the place to
start. I understand the basic concept, but have no idea on the
implimentation. I've read a bit of code on simple c sprockets and all
but I have a feeling that there is more to the design of a scalable and
secure peer to peer relation. Got any pointers?
Roarke Lynch
-------------------------------
<email_removed>
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Mon Jan 27 04:12:54 2003
On Sunday, January 26, 2003, at 11:55 AM, Jaime Magiera wrote:
> I'm a little late on this thread (been working hard)...
>
> In true Peer-to-Peer, there isn't an intermediary server to route the
> requests. Each app is both client and server, who can talk to each
> other directly. Many so-called P2P apps aren't really, since they use
> a routing server. You knock out the main server, you loose the ability
> to communicate.
>
> I'm writing as P2P app right now. It's called ThoughtConduit. It
> really wasn't to difficult -- You write some server code to receive
> data, you write some of code to send data. Right now, TC data is
> passed as SOAP messages.
>
> * We are also creating a routing app in WebObjects that can offer many
> of the desktop features to users logged in at the site. This is just
> to support those who would sacrifice true P2P for the convenience of
> doing transactions through the browser.
>
> Jaime
It might not be that difficult, but I'm looking for the place to
start. I understand the basic concept, but have no idea on the
implimentation. I've read a bit of code on simple c sprockets and all
but I have a feeling that there is more to the design of a scalable and
secure peer to peer relation. Got any pointers?
Roarke Lynch
-------------------------------
<email_removed>
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
| Related mails | Author | Date |
|---|---|---|
| Roarke Lynch | Jan 24, 02:27 | |
| mw | Jan 24, 12:53 | |
| Tito Ciuro | Jan 24, 16:00 | |
| Roarke Lynch | Jan 25, 21:20 | |
| Finlay Dobbie | Jan 25, 21:36 | |
| Ben Mackin | Jan 25, 21:53 | |
| Jaime Magiera | Jan 26, 17:55 | |
| Roarke Lynch | Jan 27, 04:12 | |
| David Remahl | Jan 27, 08:03 | |
| Jaime Magiera | Jan 27, 08:43 |






Cocoa mail archive

