See my C/S protocol thread on this Group. There *is* no ‘Wave protocol’ as you call it; the current ‘Wave’ protocol is just a federation protocol. A way for Wave servers to talk to eachother, like e–mail servers talking to eachother. You can’t write a mobile client, or really, any sort of client whatsoever, for Wave… because there is no standardized C/S protocol yet.
I’m personally itching to write an iPhone Wave client; that’s why I’m campaigning so hard for everybody to decide on a C/S protocol they like, so we can get Google to implement it on Google Wave, and then start making our clients. On Oct 1, 9:27 am, danbirlem <[email protected]> wrote: > I've yet to see much on Wave deployment going mobile. A lot of what > I've gotten my head into so far screams that Wave needs to be deployed > on the mobile front as well. Without sounding like it's the next big > thing too badly, I can foresee Wave replacing SMS in the United States > as a product of fast communication, should data networks and smart > phones catch on. Developing mobile Wave applications seems > prescadent! > > Where is the movement and support for mobile Wave protocol usage, if > the development is that far along? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
