From: Justin D. <jde...@op...> - 2006-05-31 16:01:35
|
So it looks like the resource url has to indicate to the server which service is being called somehow. In the old system we used a special WMS dispatcher mapped to the /geoserver/wms path to do it. With a single dispatcher that doesn't work. It means the dispatcher has to analyze the context path and figuring out what the request is from the context path. Interesting. So my question is now: Does it become any less correct to use the SERVICE parameter in the resource url to indicate to the dispatcher what the service is as opposed to using the context path to do it. -Justin Chris Holmes wrote: > I'm pretty positive no. In the caps document you just put the location > of the base url on to which you apply the required params. It's the > clients job to put on the required params. For example they may want a > different VERSION, 1.3 for example. If we had a dispatcher for WMS and > WFS, then their base url would be the same, and the service param would > come in to play. Also note this is one of the things cite can test, and > since we pass the tests we must be compliant. > > Chris > > Justin Deoliveira wrote: > >> Hi all, >> >> When you do a get capabilities against WMS in GeoServer you get >> Request elemetns that look like: >> >> <Request> >> <GetCapabilities> >> ... >> <Get> >> <OnlineResource xlink:type="simple" >> xlink:href="http://localhost:8080/geoserver/wms?"/> >> </Get> >> .... >> >> Since VERSION and SERVICE are required paramters on a request shouldnt >> the above be: >> >> <OnlineResource xlink:type="simple" >> xlink:href="http://localhost:8080/geoserver/wms?SERVICE=WMS&VERSION=1.1.1"/> >> >> >> -Justin >> > -- Justin Deoliveira The Open Planning Project jde...@op... |