> PPIO are needed if you want a well rounded wps client, but I don't
> see how you need them in the process api?
>  
>  

I don't.  
> And even in case of the WPS client, there is nothing to reverse engineer
> that I know of, they could be used pretty much as is.
> Can you clarify?
>  
>  

They are in the geoserver codebase; not the geotools codebase (and thus not 
available to help implement wps client).

> Ugh, but it would break the api pretty solid with quite a bit of processes
> out there already using it.
>  
>  

I would not break the API, right now AnnotationDrivenProcessFactory has the 
responsibly of assigning values
to arguments when calling a method. I figured it would be easier to give it one 
callback object that we can extend
to capture context from the execution environment; rather than have an ever 
expanding series of annotations
to keep track of. I can think of other useful examples; access to the thread 
pool or temporary storage … but perhaps
this is too complicated for the simple annotation case being used by 
AnnotationDrivenProcessFactory.  
> How about we roll two new annotations in GeoServer like this:
>  
> execute(... @ExecutionMode boolean synch, @OutputMime String outputMime)
>  
> Then GeoServer subclasses the annotation driven factory and also injects
> those two if they are found?
>  
>  

I am not as keen on using fine grain annotations as you; what we are in effect 
doing is "binding" arguments to a limited
range of control objects in order to pass down information. After a certain 
point it becomes easier to make a full process object
if you need more control.
> Makes no sense, streaming processes never support progress listener as they
> return right away and build the output as the feature
> collection/raster is traversed.
>  
>  

The Process execute method supports long running processes:

  Map<String,Object> execute(Map<String,Object> input, ProgressListener monitor)
> Where is the WPS 2.0 spec? I don't see it around.
>  
>  

Checking … does not appear to be out yet :( Last discussion I paid attention to 
was replacing "Status" and "Store" options with an explicit "async".

Jody

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to