Christian Müller ha scritto: > > > I am not sure at the moment where to place the different components of > GeoXACML > > 1) Policy Decision Point > This component handles xml stuff and authorization decisions, I think > geotools would be the right place. > The component could be used universally (like the gml stuff) > > 2) Policy Enforcment Point > I would put the base classes also into geotools, doing a special > implementation in geoserver > > 3) Policy Administration Point > This is an application for the admin, if we do that, I think geoserver is > the right place > > I assume that we will need a role based authorization, so we need > additionally > > http://docs.oasis-open.org/xacml/cd-xacml-rbac-profile-01.pdf > > which in turn I would place into geotools > > > opinions ?
For the time being I would put all of them into a geoxacml community module in GeoServer, makes it easier to develop them, build them in one shot, and does not prevent one to move them back into GeoTools when you're done, provided you make it clear what their license is. GeoServer has always tried to contribute back in GeoTools as much as possible, so nobody will try to stop you if/when you try to push them back into GeoTools (on the contrary, as I said, it's a welcomed move). Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
