Changes between Version 2 and Version 3 of ZooKernelInternal

Timestamp:

Apr 13, 2010, 3:53:03 AM (14 years ago)

Author:

trac

Comment:

--

ZooKernelInternal

@@ -9 +9 @@
 == General Principles ==
 
-ZooKernel always parse the request provided by the web server. If the request has been sent using the GET method, then the ZooKernel will treat parameters in a normal way (using KVP). To treat the POST method, ZooKernel will use the request parameter sent as an XML file containing a specific operation request document (GetCapabilities, DescribeProcess or Execute).
+ZooKernel always parse the request provided by the web server. If the request has been sent using the GET method, then the ZooKernel will treat parameters in a normal way (using KVP). To treat the POST method, ZooKernel will use the request parameter sent as an XML file containing a specific operation request document (!GetCapabilities, !DescribeProcess or Execute).
 
 ZooKernel store parsed values in a maps datastructure.
@@ -15 +15 @@
 == Requests ==
 
-==== GetCapabilities ====
+==== !GetCapabilities ====
 
-As the response to this request should simply include metadata of a services provided by a WPS server, the ZooKernel just parse the metadata file and output a well formed GetCapabilities document.
+As the response to this request should simply include metadata of a services provided by a WPS server, the ZooKernel just parse the metadata file and output a well formed !GetCapabilities document.
 
-==== DescribeProcess ====
+==== !DescribeProcess ====
 
-As the response to this request should simply include metadata of one (or more) service, ZooKernel parse one (or every metadata file for requested identifiers) and output a well formed DescribeProcess document.
+As the response to this request should simply include metadata of one (or more) service, ZooKernel parse one (or every metadata file for requested identifiers) and output a well formed !DescribeProcess document.
 
 ==== Execute ====
 
-In this case, ZooKernel first parse the metadata file to get specific requested informations, such as default value formating (if nothing was speficified in request or to check if specified was acceptable), then dynamicaly load the service shared object, try to call the process and output a well formed ResponseDocument or the returned file in case of RawDataOutput was queried.
+In this case, ZooKernel first parse the metadata file to get specific requested informations, such as default value formating (if nothing was speficified in request or to check if specified was acceptable), then dynamicaly load the service shared object, try to call the process and output a well formed !ResponseDocument or the returned file in case of !RawDataOutput was queried.