[Pywps-dev] let there be modules !!!

[Tom Kralidis]

For database I would use SQLAlchemy for DB agnostic ORM approach, which would allows support of many DBs. 

Sent from my iPhone

On 2013-05-21, at 4:01, "Jorge de Jesus" <jorge.mendesdejesus at wur.nl> wrote:

> 
> Hi to all
> 
> 
> My personal idea for the new PyWPS is that everything has to be
> extremely modular, for example:
> 
> 1 module to parse XML, (a sort of API) with well defines I/O, classes
> and methods. This allows us to decouple/couple without any problems.
> This allow us to change XML libraries on the fly, meaning if a user is
> not happy with lxml it can use a different parser module that uses DOM.
> But the module's outputs/input/methods should always be the same.
> 
> Another better example, from the WPS-DEV answers concerning the future
> WPS2.0 we will have to support things like: start/cancel/pause process
> and therefore we will have to implement some sort of database solution
> and uuid, and of course I would prefer sqlite for it but someone may
> prefer MySQL or Oracle....
> 
> This also allows for easier unittest development :)
> 
> Jorge
> 
> 
> -- 
> ISRIC - World Soil Information Post: PO box 353, 6700 AJ, Wageningen,
> The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB
> Wageningen (Bdg. 101), Office: C.013 Office Phone: +31 (0) 317 4 83715
> Mobile Phone: +31 (0) 613 9 06950 OpenPGPKey: 0xA3D0065A
> 
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev