We currently can report back with a speed strategy, that is fast but is also not guaranteed to make a proper service exception, a buffer strategy that holds the interim results in memory, and a file strategy that writes to a temp file, ensuring scalability but sacrificing some speed. These can only be set in web.xml, which while intuitive for servlet container experts is less so for normal end users. Therefor this should be configured in services.xml, along with the other global configurations.
CodeHaus Comment From: cholmes - Time: Thu, 29 Jan 2004 17:30:57 -0600
<p>I'm not sure that we <em>need</em> to do this, but it would be nice. If you don't want to do it then just close it. I think that speed strategey should be sufficient - the strategies are mostly for developers, to better debug when something goes wrong, and we can just continue to modify the web.xml file. So it's up to you Jody, if you want to roll it into GeoServer config or just close this issue.</p>
CodeHaus Comment From: cholmes - Time: Tue, 21 Sep 2004 14:18:27 -0500
<p>This is overkill, only developers need to choose the response strategy. Most should be direct to output stream, transactions however now always use a file. We should just pick the best for each response.</p>