[Pywps-devel] creating GRASS locations per default

[Jachym Cepicky]

hallo
On Sat, Nov 11, 2006 at 12:40:36PM +0000, Ludwig Max Brinckmann wrote:
> I think there are two issues: one is to support the WPS specfication, which
> will require temporary storage and this should be defined in a common way.
> The other issue are the requirements of different back-end environments,
> such as GRASS. A generic WPS framework should none of this built in, as it
> weighs things down for those who do not need it.
> I think we do agree on this.
> 
> I would suggest abstracting GRASS support out into a base class for
> processes that use GRASS, maybe as a mix-in class. Processes that use GRASS
> would inherit from it, so all general GRASS stuff stays in one place.
> 
> Such a base class could also be the model for other framework adapters.
> 
> The way pyWPS is built it should not be difficult to achieve this.
> 
> Ludwig

No, this will be no problem. I'm just thinking on backward
compatibility. With this change (and others planed), next release is
going to be 2.0.0 :-/ 

Jachym
-- 
Jachym Cepicky
e-mail: jachym.cepicky at centrum.cz
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub
-----------------------------------------   
OFFICE:                                     
Department of Geoinformation Technologies 
Zemedelska 3
613 00, Brno
Czech Republick
e-mail: xcepicky at node.mendelu.cz
URL:    http://mapserver.mendelu.cz
Tel.:   +420 545 134 514
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Digital signature
Url : http://lists.wald.intevation.org/pipermail/pywps-devel/attachments/20061111/89c9dba1/attachment.pgp