Hi Alessio,
feedback inline.
On Tue, Aug 14, 2018 at 5:32 PM Alessio Fabiani <
alessio.fabi...@geo-solutions.it> wrote:
> 1. "How do you compute the estimated completion and the next poll? Do they
> need a API change in the WPS core?"
>
> My original idea was that this remains an optional parameter, therefore no
> need to implement for every process nor to change the core itself.
> It should be used only for processes which somehow can be predicted.
> I just wanted to give to someone the possibility to tell to the client
> that the process might take a certain amount of time in case this could be
> estimated somehow.
> I envision this one more useful on specific extensions or external
> processes which have a computational method to estimate their completion.
>
Well I guess for the simple case one could use "time elapsed / percentage
complete" and then roll new extension points in case
the process or their factory have a better way.
> 3. "When does a GetExecutions request throw a DataNotAccessible,
> ServerBusy, or WrongInputData
> exception?"
>
> I envisaged those types of exceptions in order to cover some possible use
> cases especially when trying to retrieve the whole list of input/outputs
> values through the "lineage" option.
>
> In particular:
>
> - DataNotAccessible; should be thrown in the unlucky cases that the
> associated execution folder has been removed or it is somehow unaccessible
> - ServerBusy; might be thrown in the case GeoServer is locked and it is
> not temporarily able to retrieve some input values (I'm not fully sure if
> this could happens though)
>
Not really, it should not.
> - WrongInputData; originally I thought this should be thrown in the case
> someone tried to run an execution with wrong input values and therefore the
> process failed. I'm not fully sure here how the "lineage" option could
> manage this however. Any comment?
>
Mind, even using "lineage" the "input data" is not necessarily there. To
give you an example, if the request asked an external WFS for input
data, all that's found in the lineage is the WFS request itself, not the
result of it.
What the lineage stores is actually the original request in its full
form... if it happened to have the inputs inline, they should still be
there.
Cheers
Andrea
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
------------------------------------------------------- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
