[Geoserver-devel] [jira] Created: (GEOS-159) Choose the output strategy based on the request type

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GEOS-159

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GEOS-159
    Summary: Choose the output strategy based on the request type
       Type: Improvement

     Status: Open
   Priority: Major

Original Estimate: 1 hour, 30 minutes
Time Spent: Unknown
  Remaining: 1 hour, 30 minutes

    Project: GeoServer
   Versions:
             1.2.0

   Assignee: Chris Holmes
   Reporter: Chris Holmes

    Created: Thu, 22 Apr 2004 3:37 AM
    Updated: Thu, 22 Apr 2004 3:37 AM

Description:
So we came up with these response strategys of FILE, BUFFER and SPEED, but ended up not using them much since speed seemed to work pretty well for everything. I was going to make this user configurable, but it seemed a bit silly as we weren't having any errors. But it turns out that SPEED can do a little nastiness and report success for transactions that don't go through. FILE and BUFFER both catch these. This is especially relevant with our shapefiles, as people are going to (unfortunately) be trying transactions against them. I really don't want to demote everything to FILE, as that'll slow things down. I think the best thing to do is to choose the strategy based on the response. GetMap and GetFeature should do speed, getCaps don't really matter, speed should be fine, same for describe. But transaction and possibly lock should use FILE or BUFFER. Buffer may suffice as the responses are generally pretty damn small. But for the same reason file shouldn't matter too much, since the extra over head is small.

---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira