On Sun, Jan 13, 2013 at 4:48 PM, Chris Holmes <chol...@opengeo.org> wrote:
> +1 - awesome work. And I'd love to see it in 2.3.x
>
> Was there a reason other than lack of time to not make the jdbc connection
> easier to use? Like it seems to be a much more user friendly way would be
> to let users first have an option choose a datastore connection they've
> already established, instead of picking drivers and the like. And then to
> show the current thing as an advanced option. What's there now is
> definitely a great first step, and more than sufficient to get in right
> now. But am just curious if there are blockers to making things easier, or
> was just lack of time.
>
Lack of time was the number one issue, but there is more.
First off, the general design of GWC pointed in that direction, GWC is more
low level, more oriented towards the control of the little
details (e.g., for how rich the integration GUI in GeoServer is, it still
lacks some important options for production grade tile serving, like
controlling etags and expiry, or setting up cache masks to avoid caching
tiles over the sea).
Also, for how much user friendly the current datastore support in GeoServer
is still lacking a number of advanced options that one
can only control by manipulating the JDBC URL, like, try working over an
SSL connection to a postgis database or
add one of the many options the Oracle JDBC driver supports (memo to
myself, we really should provide another connection
mode allowing the advanced user to provide a full JDBC URL also for spatial
database connections).
Given that this is a enterprise feature (why setup a connection to an
external database if clustering is not needed?)
I believe it's better to err on the side of more control, instead of the
side of easier setup, and that was also agreeing with
the general lack of time context in which I've made this GWC 1.4
integration.
>
> Also what's the state of documentation with this stuff? Again, no blocker
> at all, best to get things in. We may be able to help out some with docs.
> Things like when each of the locks might make sense, to help people choose,
> and docs on the quota store configuration.
>
There is documentation in GWC regarding this, but I did not manage to make
any for GeoServer
so far, spent good part of the time I had lately to make the integration
possible to start with:
http://geowebcache.org/docs/current/production/index.html#clustering
http://geowebcache.org/docs/current/configuration/diskquotas.html#disk-quota-storage
The final deadline for new features is in 7 days, I don't believe I'll
manage to add documentation:
is there anyone interested in helping out?
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_123012
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
