@6: Eucalyptus also handles Query and REST requests along with some less well-defined HTTP requests (e.g., form POST uploads). The decision on which path the web services stack takes when parsing a request is made solely based on the contents of the HTTP start-line and headers. This is primarily because consuming the message body is not feasible in some cases. In the absence of a service path or Host header/DNS info there is not enough information to determine the destination of a request. For these reasons using SOAP namespaces is not a sufficient approach.
With respect to the Host header, from the HTTP/1.1 RFC: "A client MUST include a Host header field in all HTTP/1.1 request messages". Thus, requiring use of DNS in order to provide virtual hosting seems reasonable and sufficient. A more thorough discussion of related topics can be found in the apache vhost documentation (n.b. some of the limitations do not apply to Eucalyptus): http://httpd.apache.org/docs/1.3/vhosts/
@6: Eucalyptus also handles Query and REST requests along with some less well-defined HTTP requests (e.g., form POST uploads). The decision on which path the web services stack takes when parsing a request is made solely based on the contents of the HTTP start-line and headers. This is primarily because consuming the message body is not feasible in some cases. In the absence of a service path or Host header/DNS info there is not enough information to determine the destination of a request. For these reasons using SOAP namespaces is not a sufficient approach.
With respect to the Host header, from the HTTP/1.1 RFC: "A client MUST include a Host header field in all HTTP/1.1 request messages". Thus, requiring use of DNS in order to provide virtual hosting seems reasonable and sufficient. A more thorough discussion of related topics can be found in the apache vhost documentation (n.b. some of the limitations do not apply to Eucalyptus): http:// httpd.apache. org/docs/ 1.3/vhosts/
cheers.
chris