On Thu, Nov 10, 2011 at 4:20 PM, Justin Deoliveira <[email protected]>wrote:
> Would this be acceptable, even for the stable series?
>>
> Works for me.
>
>>
>> Also, would this have to be part of its own extension plugin, be part of
>> core
>> and spread out in the relevant modules, be part of core but be its own
>> plugin module that only web-app would depend to?
>>
>
> I would prefer an extension, since those are trivial to disable... but if
> its turns out to be too much work to do it that way then core is fine, as
> long as its relatively simple to disable by commenting out a few lines of
> spring, etc...
>
It would be a "make GS work in face of concurrent changes" extension (the
locking code I mean)
Or you were talking about the backup/restore code?
What about the locking code in core with a system variable to disable
it and backup/restore as an extension or community module?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
