Justin Deoliveira ha scritto: > Putting the philosophical debate aside for the moment there are two > things on the table here: > > 1) fast GML > 2) cite compliance with a generic setup > > The current set up can't do both without a complete overhaul of the > current gml2 encoder... which is what the gtxml encoder is. > > Also to stress the point, I only want to replace the encoder when cite > is enabled which is what? 99% percent of the time? Does anyone in > production actually run with cite enabled? > > Asking for the sacrifice of some speed in a 1% case in order to achieve > much better testing and qa of many of our datastores does not seem like > an unreasonable request to me.
I don't care if we run the cite tests a bit slower. What I'm worried about is that we would remove some test coverage on the case that people do really run in production, since the CITE tests would not test it anymore. Are you sure our unit tests provide the same coverage over GML encoding as the cite tests do? Cheers Andrea ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
