jgordijn / process Goto Github PK

Hi there :)
Though we never had the time to deep dive into it I think this is a very nice project - how about releasing it to maven central and also making sure it shows up in https://index.scala-lang.org/search?q=process ?

We nowadays have a new community page which defers all search to scaladex so this way people would find this library. http://akka.io/community/

Both PersistenProcess and Process traits have the abstract

 def process: ProcessStep[State]

This has the distinct disadvantage that when implementing this trait you have the option to define a function which returns a different object each time, which is not what you would expect.

Let just change it to:

 val process: ProcessStep[State]

@jgordijn what do you think?

since we are dealing with long running processes in some cases it's useful to be able to schedule a process step in the (near) future

Just a rough idea...maybe this deserves it's own project repo. Nevertheless, the idea is that once we can visualise the process..we could probably also turn it around and model the process visually and then have a process underneath that does the actual work.

Global abort is already supporting if I am not mistaken. Local abort might be useful too, since then one could keep the process running while pruning local (sub) process steps.

this is probably a hard one to achieve, but has great benefits when realised. The idea is to envision each process step as a function that takes input (the current state) and produces output (the transformed/updated state).

in order to make the language more fluent, strive for optional parentheses, dots & white spaces.

just a rough thought: when the process changes, probably you want to version it, such that old runtime processes can complete against the former version

these are a few rough ideas that come to mind:

• sometimes you want to perform a process step exactly N times before it completes
• OR slightly different, you want to try exactly N times before giving up
• AND optionally recovering with a failure/alternative process step

this is also still a rough idea...and it would probably deserve it's own project repo...the idea is to be able to see (visually) what the state is of a particular running process instance, so which of it's process steps have completed and which are running, etc.

Often, I want to do some validation on incoming command. To this end, it would be nice to be able to access the process state(just like in the updateState callback).

execute multiple process steps simultaneously, accept the first one that receives a response and ignore the others.

e.g. http://docs.scala-lang.org/tutorials/tour/pattern-matching.html

Although the modelled process already gives much more overview then regular Akka. Visualisation of the process would further improve it, since a picture says more then thousand words ;-)