[ZOO-Discuss] News about ZOO Kernel and ZOO Services Provider
Gérald Fenoy
gerald.fenoy at geolabs.fr
Fri Oct 1 09:58:33 PDT 2010
Hi everybody,
it is a pleasure for me to give you some informations about what happened to the ZOO Kernel and to some ZOO Services Provider during the past few weeks.
First of all I want to thanks David Saggiorato for making the ZOO Kernel supporting the Perl Language, so now you can code your new Services Provider using this programming language. Then, another special thank to him for his work on improving the autoconf tools use for the ZOO Kernel compilation process. Now, even Python is optional, you don't have no more to use the --with-<MY_LANGUAGE>=no but simply use the --with-<MY_LANGUAGE> option with or without argument depending on your local environment.
As thanks to David we get one more language which can be spoken by ZOO Kernel, it is now also able to speak many natural languages. In fact the natural languages you teach it. Obviously one more time we didn't do that much and searched for relevant technologies to achieve this goal. Hopefully with the help, experience and knowledge of Markus Neteler we were able to decide fast that we have to use gettext for this. So we used some technics already used in GRASS software to create our own mechanisms to make translation available and working in the ZOO-Project.
You can take a look at this page http://zoo-project.org/trac/wiki/ZOOTranslation to get more information about the way to create the translation file for your language and start the translation effort. Hope to find some volonteers to help in this translation effort.
ZOO Kernel is now able to display current status information about a running ZOO Service when it was runned as a background task. We've implemented a function called UpdateStatus which can be used by ZOO Services to update their current status information. We also added a specific environment section for the main configuration file maps called "lenv" an which is used to store both sid (Service ID), status and can also store a message string. This message string will be used by ZOO Kernel to fill the ServiceFailed node if case your service failed (one more time those messages can be now translated also :) ).
The updateStatus function can be used from both C and JavaScript by now. As you can see in the followings urls (yes sorry for the long urls I provide here :) ) :
* C program called longProcess (available in wps_status Services Provider) : http://www.zoo-project.org/cgi-bin-new/zoo_loader.cgi?request=Execute&service=WPS&version=1.0.0&Identifier=longProcess&DataInputs=S=t&storeExecuteResponse=true (add &language=fr-FR to get it translated in french :) )
* JavaScript program called demoJs : http://www.zoo-project.org/cgi-bin-new/zoo_loader.cgi?request=Execute&service=WPS&version=1.0.0&Identifier=demoJs&DataInputs=S=t&storeExecuteResponse=true (add &language=fr-FR to get it translated in french :) take care that demoJs is fast, to loose time from JavaScript we used some ZOORequest so you'll have to be fast to see it working)
Obviously same support is available for the mandatory POST requests.
Many other things have been corrected and code was a bit improved.
Hope to get feedbacks from you on this news version,
best regards,
Gérald Fenoy
gerald.fenoy at geolabs.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-discuss/attachments/20101001/1ee97587/attachment.html>
More information about the Zoo-discuss
mailing list