At Fri, 10 Jul 2009 21:01:14 -0700, Julian Cain wrote: > > > On Jul 10, 2009, at 8:01 PM, Eric Rescorla wrote: > > > At Fri, 10 Jul 2009 19:51:53 -0700, > > Julian Cain wrote: > >> > >> > >> Why would a node send the "purpose of the connection" in it's Attach? > >> Attach is low level and hardly indicative of anything Overlay > >> related. > >> The Attach clearly states the purpose of the connection outright, > >> what > >> we do not is the reason for the Join and what role the joining node > >> wishes to assume. > > > > What do you mean? Only nodes which are going to store data send > > joins. That's what Join means. > > Technically Join doesn't mean or indicate nodes that "are going to > store data", instead Join indicates a node that WANT's to store and > route.
Sure, but "store", not "route". If you don't send updates, you won't be routing. > If the join_req fails the Client is still a Client otherwise it > sends a series of Store's along with Update's and only then is the > node considered a Peer inside of the ring vs a Client outside of the > ring. Actually, the node (formerly Client) does not send Stores. Rather, the peer that it's taking over space from sends Stores. The node can of course send its own Stores to store data at any time. > I assume this AppAttach performs an Attach and then the AppAttach > instead of a Join? AppAttach (when it exists) doesn't have anything to do with clients. It's what you use to initiate connections for traffic other than RELOAD. RELOAD technically supports this already with hte application field, but our experience with implementatons was that people found using the same method for both purposes was really confusing. -Ekr _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
