Serge, http://www.nimbleseal.org brings NOT FOUND page.
Monika On Sep 8, 4:00 am, Serge Slipchenko <[email protected]> wrote: > On Sep 8, 6:16 am, Tad Glines <[email protected]> wrote:> > Essientially > if you did so the client would become a server, and have to be > > > reachable 24 hours a day. > > > I probably should have been clearer about what I'm proposing. What I > > should have said was that we can use the existing messages, but with > > different semantics. > > The s2s is more of a push model, with some request/response thrown in > > and the assumption that the server is almost always on. For c2s a more > > traditional pubsub model is needed. > > I agree with you that the sufficient client/server protocol already > proposed inhttp://xmpp.org/extensions/xep-0060.html. > Those protocol already has item discovery, access control, > subscription and notification functions. > I think that FedOne implementation of the client/server protocol > through the RPC calls is a step backward. > But we should not forget that FedOne is just a mock-up. > That's why in our projecthttp://www.nimbleseal.orgwe have chosen two- > stage strategy of development. > At the first stage we want to implement the python client library > based on RPC interface provided by FedOne. > At the second stage we planning to implement python wave service > component and client library based on PubSub, > -- > Serge --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
