Jody Garnett wrote: > Hi Justin: > >> Recently OpenGeo has received funding to implement the idea of virtual >> services in a limited form. The basic idea is to provide service >> endpoints for each workspace so you can make requests like: >> >> http://.../geoserver/topp/wfs?request=.... > > So "topp" is the name of the service being offered in the above request. One > question is the following valid. > > http://.../geoserver/topp?Request=GetCapabilities&Service=WFS&Version=1.1..... > > I am trying to see if the service really is "topp" and the service supports > one or more protocols... Yes, that is the idea. Of course at the moment we don't have the ability to turn off any of the services (aside from security). > >> Basically what we currently do with workspace filters as a query >> parameter with some additions. The full GSIP is written up here: >> >> http://geoserver.org/display/GEOS/GSIP+44+-+Virtual+services+with+workspaces >> >> One thing to note is how this plays with resource publishing split since >> there is some overlap in this functionality and what resource pub split >> will provide. I wrote up some notes at the end of the proposal on this. >> But the gist of it is that the upgrade path should be quite smooth. > > Thanks Justin it is a well written proposal; the only section I had trouble > with was the security implications. It is unclear if the approach you are > advocating here is a change to the default security subsystem; or just an > approach to use how to handle security at a future point in time? If it is a > change for right now could you provide an example snippet of how to configure > what you are describing? The security implications are that if you plan to use a specific workspace endpoint, do not expect to be able to access layers from other workspaces. There will be zero configuration required. > >> Actually this work fills one of the gaps that was shot in the resource >> pub proposal by Jody in that it did not explicitly specify the ability >> to specify a map in a url path as opposed to specifying it in the query >> string. > > Thanks I picked up - and think the URL will be much more stable in this > respect. Agreed, looks much nicer. > >> Comments and feedback welcome. > > One assumption and a question > > I assume this work needs to be made available in the stable 2.0.x series. > WIth that in mind what is your deadline for this work, and does the deadline > include the functionality being issued as part of a release. Yes, I will need this work to take place on the stable branch. As for when to release the date can be flexible. Since 2.0.1 is coming soon (or so i hear ;)) I would think targeting 2.0.2 would make most sense. >
-- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
