There is no server-side limiting mechanism at the moment. The limiting mechanism is purely on the MaestroAPI side.
Having said that, if you're using MGOS 2.5 or newer, feature query responses are now chunked meaning content will be written out to the wire as the server-side feature reader is being iterated upon. There is very little internal buffering of the reader content on the server-side. We only buffer enough content in order to transmit a valid chunk of XML or JSON - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Limiting-number-of-results-from-Maestro-QueryFeatureSource-or-mapagent-SELECTFEATURES-tp5135715p5136595.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
