I've a patch for it: <http://github.com/groldan/geoserver_trunk/commit/4340a98fd0a4c04e33755b9b8cba46b631c49713>
Which allows to truncate caches only for the transaction's affected area and iif the transaction was successful: <http://github.com/groldan/geoserver_trunk/blob/081231f33b229ff17f54476a620ef260a80d7df4/gwc/src/main/java/org/geoserver/gwc/GWCTransactionListener.java> Comments? Cheers, Gabriel On Aug 17, 2010, at 5:59 PM, Gabriel Roldan wrote: > Hey all, > > I'm in the process of avoiding GWC to whip out the whole layer cache upon > every transaction. > > To that end, I need to make good use of transaction events, but to make > _good_ use of them I'd need two things: > - first, currently only update transactions issue post events. Insert, update > and delete issue pre events. > - second, it'd be great that post events were always thrown. I think the > rationale behind not issuing post events for insert and delete is that the > affected features won't change. But still id't be good to have a sense of > whether a given transaction succeeded or failed. So a > reasonForFailure():Exception property in TransactionEvent would be great, > provided post events are always thrown, both upon success and upon failure. > > Thoughts? may I add post events to insert and delete transactions, and before > throwing a service exception? > > Cheers, > Gabriel ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
