The system of course will have central components which will be used for crypt key enrollment and user authentication. But I doubt that existing P2P VoIP systems use these login/authentication servers for tracking user sessions. If this task can be handled by P2P network why should we issue additional requests to costly centralized infrastructure? Of course if it *cannot* then I'll have to implement centralized session tracking.
2009/5/30 David Barrett <dbarr...@quinthar.com> > leviant Leviant wrote: > > > > I do not want (at least yet) to implement any central component for such > > purposes. > > I guess I'd ask: why this design constraint? The only practical benefit > I can see to a "pure" decentralized design is protecting yourself from > forced shutdown. But even that can be mitigated by having servers in > different jurisdictions. > > Basically, if you're saying "I just want to build cool tech and that > sounds fun", that's a totally valid reason. But if you're trying to > build a scalable, secure, high-performance, real-world usable system, I > see no reason to avoid central components. > > -david > > _______________________________________________ > p2p-hackers mailing list > p2p-hackers@lists.zooko.com > http://lists.zooko.com/mailman/listinfo/p2p-hackers >
_______________________________________________ p2p-hackers mailing list p2p-hackers@lists.zooko.com http://lists.zooko.com/mailman/listinfo/p2p-hackers
