Quoting Jody Garnett <[EMAIL PROTECTED]>: > So GeoServer is not used to clients hanging up on it? I bet you are > making requests based on user interface events, > and are not paying attention to if any outstanding requests are already > in process...
This is true... but this isn't caused by me clicking wildly; it fails on the first shot, i'm just passing it a feature collection -- i'll investigate how that featurecollection is obtaining and if there are more sensible ways to obtain it. > Short Term Solution: > Alternative 1: take a "representative sample" (first 1000 features) - > hold it in memory - and use it to answer your questions as the user > interface state changes. This is occurring on topp:states -- there are only 48 features. > Long Term Solutions: > Alternative 2: extends the WFS specification with additional operations > to get the information you need - so you can get the unique values of > attribute "category" for example, or the min/max of "height". > Alternative 2: extend the WFS specification with a vendor parameters for > "Sample" which would ask for a sample set defining the range of values > possible ... This seems rather extreme for something that was working a few weeks ago! Thanks, Cory. ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
