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

[Jachym Cepicky]

Agreed,

right now, I'm approaching with input parsing. Thought dependent on lxml.

Current approach (in general) uses following style (in general):


input = new Input()

input.set_from_xml(node) # xml node from lxml.objectify

# or

input.set_from_url(url_string)

maybe "parse_from_*" would sound better

I did not come to the "database" part yet, but sqlite is my favourite here.

TBD

Jachym


Dne 21.5.2013 09:45, Jorge de Jesus napsal(a):
> 
> 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
> 
> 

-- 
Jachym Cepicky
Help Service - Remote Sensing s.r.o.
jachym.cepicky at gmail.com
HS-RS: jachym at hsrs.cz http://bnhelp.cz
http://les-ejk.cz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20130521/a527bcc9/attachment.pgp>