2010/11/24 Graham Simpson <[email protected]> > 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. >
Yep, the other discovery methods are there to enable federation without DNS access. The easier it is to setup federation, the more people will do so (hopefully) > Can I assume that an a direct-service http method, the same server > port/interface will host both the web client and the federation? Am I > There are several options: a) The wave server is standalone and does its HTTP stuff by himself b) A web server is in front and delegates everything starting with /fed/wave/.... to the wave server via FCGI c) A load balancing server redirects requests to either a web server or the wave server just by inspecting the URL In general, we inherit all the HTTP goodness. > 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! > This is definitely one possible solution. Wave can distinguish web/federation-wave/client-wave just by inspecting the URL. Thus, it is possible to run it all on a single port. Using DNS you can choose any port you see fit. Greetings Torben > > 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%[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]<wave-protocol%[email protected]> > . > 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.
