There's no login & authentication process in the current protocol. Until that is added in, it will be impossible to use the client-server protocol on 'real' servers.
-J On Sat, Jun 26, 2010 at 9:19 PM, Toshiya Kazuyoshi <[email protected]>wrote: > The new opensorced Client Code can talk to our own server. Is there a > way to talk to wavesandbox.com directly not by server federation? Or > maybe in the future, is it possible? The Google Wave Client-Server > Protocol Whitepaper says "There are many things that are not covered > by this specification at this time, such as authentication, > authorization, how a client determines which server to talk to, or > which port to use.". > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- 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.
