The hope is to prevent the creation of more "unsafe" names on disk (so I do
not expect to see foo__bar and foo::bar).
The goal was to recognize we have introduced ambiguity and cut it off
before the problem gets worse.
--
Jody Garnett
On 27 January 2015 at 10:39, David Winslow <dwins...@boundlessgeo.com>
wrote:
> The proposal to automatically rewrite names seems pretty complicated. I
> have a number of concerns but I want to focus on just one:
>
> The goal is to eliminate ambiguity but the proposal seems to be adding
> it. What should happen if a user has an existing configuration with two
> styles - one named "foo__bar" and another named "foo::bar"? Or generally
> how do we avoid having multiple "unsafe" names translating to the same
> "safe" one? I don't think that it is possible to do this and keep it
> transparent to old clients.
>
> On Tue, Jan 27, 2015 at 1:19 PM, Jody Garnett <jody.garn...@gmail.com>
> wrote:
>
>> Here is the proposal:
>> https://github.com/geoserver/geoserver/wiki/GSIP-127
>>
>
>
>
> --
> David Winslow
> Software Engineer | Boundless <http://boundlessgeo.com/>
> dwins...@boundlessgeo.com
> 917-388-9085
> @boundlessgeo <http://twitter.com/boundlessgeo/>
>
>
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
