Skip to content

Simplify app development with dedicated API for tasks not depending on volatile process state #25

@Viir

Description

@Viir

So far, we always use volatile processes to run tasks integrating other software.
However, in many cases, we don't need the facilities to retain volatile process state beyond a single task. Examples are usages of elm-format and elm make in Elm Editor.

A dedicated API for a single task would simplify application developers' implementation. For example, this part should be simpler (And more complete, forwarding any errors that were not linked to RequestToVolatileProcess):

Err Platform.WebService.ProcessNotFound ->
( httpResponseInternalServerError
("Error: Volatile process '"
++ pendingTask.volatileProcessId
++ "' disappeared. Starting volatile process again... Please retry."
)
, Just pendingTask.volatileProcessId
)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions