Fair enough, good arguments for making it part of the default distro. I just always think that a very lean and plain core with extensions makes for a nice architecture. But from a product/functionality standpoint it makes sense to include it.
However I do think a plain geoserver with no frills is something that people might want. I could be wrong here... i would be interested in hearing some users take on this. Perhaps we can can call it geoserver-vanilla-bin.zip and make it another artifact. If it is to be included then suggest we move it from a community/extension module... and just into main. For one so that we don't have to remember to build releases with the geowebcache profile, and two it will mean that extensions we put up for download match extensions modules in the code base. -Justin Chris Holmes wrote: > What do you mean by an artifact with gwc baked in? Like a set of binary > downloads that geoserver+gwc-1.7.0? > > I think it makes sense to start including gwc directly in the default > release, not forcing people to download a separate jar and plug it in. > For one the KML super overlay code relies on it directly. And > eventually I'd like to make it so our layer preview uses gwc directly - > with it automatically killing the cache when you change the config or > the style or do a transaction. Then geoserver will always tile things by > default, which I think is a huge win. > > It should be kept as a separate module, but I think it should be > included in the release. I see it as more on the level of like WCS, a > service that should ship by default. Eventually we may make a slimmed > down release, but for now we already include the kitchen sink. > > C > > Justin Deoliveira wrote: >> Hi Arne, >> >> How do you want to go about including it? Like baking it directly into >> the release? I myself would like extensions to be kept as extensions, >> downloadable separately. However I am all for including an additional >> artifact with gwc "baked" in. >> >> -Justin >> >> Arne Kepp wrote: >>> Hi, >>> >>> for the upcoming RC release of GeoServer 1.7.x we would really like >>> to include the GeoWebCache module to demonstrate new superoverlay >>> functionality (for Google Earth and other KML clients). >>> >>> Does anyone object / feel we need to go through a more formal process? >>> >>> It does not modify code in GeoServer, the memory footprint is tiny >>> and it uses HTTP to communicate with the core. If invoked, it creates >>> a "gwc" folder in the data directory or the temp directory. >>> >>> -Arne >>> >>> ------------------------------------------------------------------------- >>> >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge >>> Build the coolest Linux based applications with Moblin SDK & win >>> great prizes >>> Grand prize is a trip for two to an Open Source event anywhere in the >>> world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> Geoserver-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >>> >>> >> >> > > > !DSPAM:4007,4888cbfd188126491211187! -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
