Many clients are not intelligent enough to handle different url locations for different operations. While they are technically not compliant with the spec, we should make an effort to support as many clients as we can. They are expecting pure cgi style, with all requests having the same base url. We can handle this with this dispatcher, we just need to be able to report to the clients where the dispatcher is.
After we start to detect where requests came from this should be easier to implement. I'm a bit reluctant to have all capability docs report through the dispatcher, as it introduces a bit of not so necessary overhead, and would add another layer for something to go wrong.
CodeHaus Comment From: cholmes - Time: Thu, 29 Jan 2004 18:28:27 -0600
<p>This shouldn't be too difficult in 1.2, as we can now get what the actual request issued was. We just need to figure out which went through the dispatcher servlet (the easy way is just checking to see if it contains geoserver/wfs?...) And if so then the capabilities should return in that style. Note this is only for get requests - we haven't yet figured out post requests, as the servlet seems to only let you read the input stream once. We can try saving the stream or something... But I think most people just care about getting the get requests in this form.</p>
CodeHaus Comment From: dzwiers - Time: Mon, 2 Feb 2004 18:23:07 -0600
<p>Fixed for get capabilities only. Easy enough for anothers that may require it. (see WfsCapabilitiesResponseHandler)</p>