+1 for me. This could be quite useful for app-schema deployments, because app-schema is a database connection hog (and uses multiple connections to service a single request [naughty, naughty]), so control flow could be used to limit the number of requests to avoid connection pool deadlock in production deployments. Niiice.
On 03/06/10 21:23, Andrea Aime wrote: > Hi, > I would like to propose we move the control-flow extension to > extensions in both 2.0.x and trunk. > > Rationale: > - I have been using it for 4 months on demo.opengeo.org/geoserver > with good success, the box has been quite stable so far and without > performance issues > - it is documented: > http://docs.geoserver.org/stable/en/user/community/controlflow/index.html > - has a maintaner (me) > > PSC, what do you think? Btw, shall I do a formal proposal or a mail is > enough? ;-) > > Cheers > PSAndrea > -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
