On 26-05-17 03:22, Ben Caradoc-Davies wrote:
It still seems to me that "workflow" is a very general term. What
workflow patterns <https://en.wikipedia.org/wiki/Workflow_patterns>
will you support? Could future extensions support BPEL
<https://en.wikipedia.org/wiki/Business_Process_Execution_Language> or
YAWL <https://en.wikipedia.org/wiki/YAWL>?
I am not objecting to what you are trying to do, which sounds very
useful, just worried that the name might mislead as to scope.
Could your module be described as "stored-procedure" or
"server-procedure"?
"There are only two hard things in Computer Science: cache
invalidation and naming things. -- Phil Karlton"
https://martinfowler.com/bliki/TwoHardThings.html
Okay Ben, you make a good case, we can pick another name to avoid
confusion.
I'll have a think and discussion about it. "Stored procedure" that
reminds me too much of stored procedures in databases though.
What I mean to ask is whether the tasks are scripts, REST API calls,
pluggable providers, or some means?
ah, pluggable providers.
Regards
Niels
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
