On 11/24/2010 03:51 PM, Graham Simpson wrote: > Ok, that makes a lot of sense. I'm not sure of the need to have the > second and this discovery options, rather than just the dns record - > still, they don't detract from general operation for most users and > provide additional options for some situations, such as government > organisations with limited access to their DNS systems. > > Can I assume that an a direct-service http method, the same server > port/interface will host both the web client and the federation? In a very simple case, it could be, but I wouldn't make that assumption, it's not how we'd run the service.
Am I > also right in thinking that this will provide a websockets interface > for other clients - again on the same port? If this is the case, it's > another massive bonus for the http method, because it means all > communication with the server can be achieved on a single arbitrarily > selectable port! > > On Nov 24, 8:17 pm, Torben Weis <[email protected]> wrote: >> Hi, >> >> discovery with HTTP federation is described here: >> >> http://www.waveprotocol.org/protocol/design-proposals/http-based-fede... >> >> <http://www.waveprotocol.org/protocol/design-proposals/http-based-fede...>Of >> course you can setup virtual hosts using standard HTTP techniques which >> allows you to operate multiple domains on one server or to re-route requests >> depending on the target domain name. It comes with HTTP for free so to say. >> >> Greetings >> Torben >> >> 2010/11/24 Graham Simpson <[email protected]> >> >> >> >> >> >>> My questions are always dumb and obvious: Wave over XMPP used the XMPP >>> protocol discovery using a specific DNS record... Wave ov HTTP - you >>> haven't described how the discovy works for HTTP yet, or is that in a >>> document that I haven't read? Likewise, will this simply run over port >>> 80 like any other web service, or is there a defined 'wave' port? >>> Another nice feature of wave over XMPP is that you could have 5 >>> different services talking over the standard XMPP port because the >>> server directed the traffic to the right extension based on the >>> content - how does that work with regard to HTTP, for environments >>> with a single public IP address? (e.g. a home static/dyndns >>> environment) >> >>> -- >>> 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%2bunsubscr...@goog >>> legroups.com> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/wave-protocol?hl=en. >> >> -- >> --------------------------- >> Prof. Torben Weis >> Universitaet Duisburg-Essen >> [email protected] > -- 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.
