[Mapbender-dev] motion: change file system layout

[Samson, Marko]

+1 to the new filesystem structure.

And I like the additions of Melchior.

Viele Grüße,
Marko Samson

-- 
Marko Samson
Landesbetrieb Wald und Holz NRW
GIS-Anwendungsentwicklung
Referat I-5
Albrecht-Thaer-Straße 34
48147 Münster

Tel.:   0251/91797-166(Montags)
        05771/913455(Freitags)  
Mail: marko.samson at wald-und-holz.nrw.de
  

> -----Original Message-----
> From: mapbender_dev-bounces at lists.osgeo.org 
> [mailto:mapbender_dev-bounces at lists.osgeo.org] On Behalf Of 
> Melchior Moos
> Sent: Monday, July 07, 2008 9:25 PM
> To: Mapbender Developer List
> Subject: Re: [Mapbender-dev] motion: change file system layout
> 
> +1 I like the idea of a more structured filesystem.
> Why not add a plugin/  directory which has the same function 
> as the mod directory but contains all modules the are not 
> shipped with mapbenders standard installation? This would 
> lead (in theory) to a clear division between customations and 
> core code. This would be the place where the <project 
> name>_<module name> modules would be.
> 
> Christoph Baudson schrieb:
> > As most of Mapbender's recent security issues stem from files being 
> > unnecessarily in the http folder, I think we should move as 
> many files 
> > as possible out of that directory. Only files which are 
> really loaded 
> > via http should remain there.
> >
> > <motion>
> >
> > I motion to
> >
> > - move the PHP classes from /http/classes to /lib (and remove the 
> > prefix "class_"). We can keep wrappers for the sake of backwards 
> > compatibility (an old class file would only include a new 
> class file).
> > - move the external libraries from /http/extensions to /ext
> >
> > - create a folder /mod which holds a folder for each module 
> (example: 
> > /mod/mapframe1). Move files from /http/php and /http/javascripts to 
> > these folders
> >
> > in Mapbender 2.6 (est. release date Sep 15, 2008) </motion>
> >
> > I already have a working experimental version in 
> > /branches/testbaudson_dev.
> >
> > The rest will remain untouched now, but will be moved to the new 
> > folders later on (there is no need for http/frames, http/html, 
> > http/include, http/print). I'm not sure how to deal with 
> > http/javascripts and http/php, maybe we should have a 
> http/mod folder 
> > as well? I'm also not sure about /http/sld.
> >
> > This approach also helps to
> > - isolate modules from the core
> > - optimize the core
> > - remove deprecated modules
> > - exchange modules
> >
> > For customizations, we recommended to add a folder /http/x_<project
> > name> in the past. This folder could be replaced by folders
> > mod/<project name>_<module name>. This would help us to integrate 
> > modules developed for specific scenarios into the Mapbender generic 
> > development, and also to update overwhelmingly customized 
> Mapbenders.
> > Sustainability is the keyword.
> >
> > Christoph
> >
> 
> _______________________________________________
> Mapbender_dev mailing list
> Mapbender_dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapbender_dev
>