On Fri, Jul 13, 2018 at 3:06 PM, Alessio Fabiani <
alessio.fabi...@geo-solutions.it> wrote:
> I forgot to mention that the processes running on the backend for the use
> case I was speaking about, are so heavy that the time spent to produce the
> outputs might be negligible.
>
Yep, just remember
On Fri, Jul 13, 2018 at 3:04 PM, Alessio Fabiani <
alessio.fabi...@geo-solutions.it> wrote:
> Hi Andrea,
> not sure this is useful for our real use case. In our case we can send
> this estimate from the backend. In particular we are using the "wps-remote"
> plugin which completely relies on backen
I forgot to mention that the processes running on the backend for the use
case I was speaking about, are so heavy that the time spent to produce the
outputs might be negligible.
Il giorno ven 13 lug 2018 alle ore 15:04 Alessio Fabiani <
alessio.fabi...@geo-solutions.it> ha scritto:
> Hi Andrea,
>
Hi Andrea,
not sure this is useful for our real use case. In our case we can send this
estimate from the backend. In particular we are using the "wps-remote"
plugin which completely relies on backend processes decoupled by an XMPP
layer.
Nevertheless, my intention is to include this parameter on t
Hi Alessio,
thanks for the useful feedback. Notes inline.
On Thu, Jul 12, 2018 at 12:30 PM, Alessio Fabiani <
alessio.fabi...@geo-solutions.it> wrote:
>
> *Executions List*
> At a first glance I was thinking to the possibility of having some
> "public" executions, somehow, but digging a bit more
Hi Alessio,
a few questions to help clarify your proposal:
- Right now the list of executions is visible only to the administrator
via the GUI. How does this request work authorization wise? Anyone can see
all executions? Or only the ones he started as an authenticated user?
- What inf
