A typical corporate firewall policy is to block non-HTTP traffic, and force HTTP traffic through a proxy. For e-mail this means that you can get to GMail via their web interface, but not via POP or IMAP. The Wave corollary is that you will be able to get to Google Wave via their web interface but not via any non-HTTP based client interface.
Saying that Wave needs to support a HTTP based client/server protocol is like saying that e-mail needs to support an HTTP based client/server protocol. If the wave client/server protocol ends up being XMPP based, it will be up to the provider to turn on BOSH support. On Mon, Oct 19, 2009 at 1:14 AM, Jeroen Janssen <[email protected]> wrote: > > On Fri, Oct 16, 2009 at 7:01 PM, Joe Developer > <[email protected]> wrote: >>> > If your corporate firewall does not allow XMPP, your federated server >>> > will not be able to participate, either. >> >> Not everyone who wants to use a client behind a firewall will be running a >> federation server ;) > > That was exactly what I was trying to point out. > > If the public google wave service will eventually use the > client/server protocol that is being defined here, I still want to be > able to use it from any corporate network (through a http proxy). > > Not everyone will want to setup their own federation server inside. > > Best regards, > > Jeroen Janssen > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
