Hello, Le 29 nov. 2009 à 01:22, Mickaël Rémond a écrit :
> Le 23 nov. 2009 à 01:29, Shadowriver a écrit : > >> I would go with XMPP, just for fact that most current foundation >> server projects already works as XMPP server components, implementing >> c/s would be easier, also XMPP have lot of ready to go features that >> can be used on wave. Besides, Wave is already one foot on XMPP, why >> complicate life to making c/s in completely different format then s/s, >> it would be some sort of "understandable island" for XMPP clients in >> there network. Whatever happens, i think XMPP will end up having wave >> c/s support anyway, if not by this team then by others, existence of >> wave components on it's network just yell to do that. As an addition to my previous mail: We already forsee several points that need to be integrated from the beginning in the XMPP client approach. For example, people will get possibly reluctant to share directly their password with a client / wave reader / notifier. It is important to allow delegation of right (through a mecanism like Oauth for example), so they they can grant temporary and limited access to the client (read only access for example). -- Mickaël Rémond http://www.process-one.net/ -- 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.
