On Thu, Dec 15, 2011 at 7:45 AM, Andrea Aime
<andrea.a...@geo-solutions.it>wrote:
> On Thu, Dec 15, 2011 at 12:19 AM, Justin Deoliveira
> <jdeol...@opengeo.org>wrote:
>
>> Thanks Andrea, I think this way is much cleaner as well. And we can
>> minimize api impact by keeping all the methods on GeoServerInfo intact (but
>> deprecated) for now.
>>
>> Question about names. What should the new interface be called?
>>
>> SettingsInfo
>> LocalSettingsInfo
>> ServiceSettingsInfo
>> WWWSettingsInfo
>>
>
> It's been so long since we named something www, we should give it a go
> again :-)
>
> Judging from your screenshots later in the thread WorkspaceSettingsInfo
> might be a
> good fit.
> At the same time, that's stuff one can configure also globally, so it's
> not only
> workspace. SettingsInfo could be a way, or maybe we could split them by
> topic and have OrganisationInfo and so on.
>
>
Yeah, while it makes some sense this new interface is going to accessible
from the global GeoServerInfo as well... so it can be global or
workspace specific as you say.
For now I have gone with SettingsInfo... but am open to something different.
> I had a go into GeoServer info and I see things that are obvious
> candidates
> (such as ContactInfo) and things that are less.
> For example take proxyBaseURL, in a multi-tenancy/Service provider scenario
> one might have a single GeoServer for many organisations, each one having
> its own public first or second level domain, some might want to use OGC
> standard schema references and other not, each one might need to use
> a different default charset and so on.
>
Yeah, the form in that screen shot was not complete. MOre stuff is pulled
in. Here is the entire interface.
https://github.com/jdeolive/geoserver/blob/workspace_settings/src/main/src/main/java/org/geoserver/config/SettingsInfo.java
Basically the only things not pulled into it are:
* jai
* coverageAccess
* updateSequence
* adminUsername/adminPassword
* featureTypeCacheSize
* xmlPostRequestLogBufferSize
* globalServices
A case could be made for some of them... maybe updateSequence?
>
> Some of these are organization related (OrganizationInfo?) others are
> settings that affect all the services (base urls, we could call those
> ServicesInfo?) and so on, others are clearly global such as the JAI
> settings (since they affect the JAI singleton) so they have to stay
> in GeoServerInfo
>
> Ok, enough ranting for now :-p
>
Thanks for the feedback!
>
> 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
> mob: +39 339 8844549
>
> 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
>
> -------------------------------------------------------
>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT complexity
while improving strategic productivity. Learn More!
http://www.accelacomm.com/jaw/sdnl/114/51507609/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
