That is where we ended up (again) ... so good that you are happy.
One thing you may be able to speak to is the suffix to prevent name clashes
- it looks like this is only to untangle updating an old catalog. Is there
any way we can confine that logic to *just* the upgrade process (and thus
have an easier validation story to tell when renaming styles).
--
Jody Garnett
On Tue, Jun 3, 2014 at 3:21 AM, Justin Deoliveira <[email protected]
> wrote:
> Sorry, chiming in on this one late. If we are talking about moving the SLD
> content inline then doesn't that rule out storing styles in other languages
> (ie CSS)? This is actually something I am looking at doing sooner rather
> than later for a client. So if this gets moved inline I'll need a way to
> specify that the content is stored externally.
>
> In general I don't really like the idea of storing the contents inline
> although that may just be because i am used to the current way of things.
> But i do feel that having the contents separated is more flexible. All in
> all I like the idea Andrea originally proposed and that is detecting the
> conflict and just using a suffix to ensure there are no file names clashes.
>
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
