Hi all,
It seems a little confusing that we call the rest configuration extension restconfig-*.jar, while the link text (and documentation section) for it just say REST. To make it even worse, there is a rest-*.jar that is included in the default GeoServer distribution!
I think it would clear things up a bit if we:
* Started calling the "rest-config" module "REST Config" in documentation, or
* Renamed the "rest" module rest-support (and renamed rest-config to just "rest" if we're documenting it that way.)
Any objections?
--
David Winslow
OpenGeo - http://opengeo.org/
Agreed, and this one is indeed my bad.
I vote we just start documenting it as restconfig.
Actually I would prefer we start referring to it as "httpconfig" since that is really more indicative of what it is.
-Justin
On 2/23/10 11:06 AM, David Winslow wrote:
Hi all,
It seems a little confusing that we call the rest configuration
extension restconfig-*.jar, while the link text (and documentation
section) for it just say REST. To make it even worse, there is a
rest-*.jar that is included in the default GeoServer distribution!
I think it would clear things up a bit if we:
* Started calling the "rest-config" module "REST Config" in
documentation, or
* Renamed the "rest" module rest-support (and renamed rest-config to
just "rest" if we're documenting it that way.)
Any objections?
--
David Winslow
OpenGeo - http://opengeo.org/
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
This is just my 2 cents, but if we're looking to rename the restconfig module I would prefer a more abstract name over a more concrete one (ie, mention less about the implementation, rather than more). How about "remote control"?
--
David Winslow
OpenGeo - http://opengeo.org/
On 02/23/2010 11:22 AM, Justin Deoliveira wrote:
Agreed, and this one is indeed my bad.
I vote we just start documenting it as restconfig.
Actually I would prefer we start referring to it as "httpconfig" since
that is really more indicative of what it is.
-Justin
On 2/23/10 11:06 AM, David Winslow wrote:
Hi all,
It seems a little confusing that we call the rest configuration
extension restconfig-*.jar, while the link text (and documentation
section) for it just say REST. To make it even worse, there is a
rest-*.jar that is included in the default GeoServer distribution!
I think it would clear things up a bit if we:
* Started calling the "rest-config" module "REST Config" in
documentation, or
* Renamed the "rest" module rest-support (and renamed rest-config to
just "rest" if we're documenting it that way.)
Any objections?
--
David Winslow
OpenGeo - http://opengeo.org/
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
David Winslow wrote:
This is just my 2 cents, but if we're looking to rename the restconfig module I would prefer a more abstract name over a more concrete one (ie, mention less about the implementation, rather than more). How about "remote control"?
I have the impression we have marketed the "REST config" name enough
in blogs, docs and discussions that it would be counter productive
renaming it.
The rest module is instead something internal, only of interest to
developers, so it's actually easier to rename it to rest-support
(which sounds like a good idea to me)
Cheers
Andrea
On 2/23/10 12:47 PM, Andrea Aime wrote:
David Winslow wrote:
This is just my 2 cents, but if we're looking to rename the restconfig
module I would prefer a more abstract name over a more concrete one (ie,
mention less about the implementation, rather than more). How about
"remote control"?
I have the impression we have marketed the "REST config" name enough
in blogs, docs and discussions that it would be counter productive
renaming it.
The rest module is instead something internal, only of interest to
developers, so it's actually easier to rename it to rest-support
(which sounds like a good idea to me)
Well to me the "support" suffix seems overly verbose. But if we did go that route we should rename "ows" to "ows-support" as well, and any other module that did not actually contribute a service or something visibly functional but is only there as a building block or "support" module.
Cheers
Andrea
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.