The current layout of an Ambition application doesn't actually make sense, and it's due to some experimentation with how to handle bad code and segmentation faults. The ambition run and ambition monitor commands are simple runners that allow an application to stay running when the developer makes a mistake, but they don't actually do any failure handling or trapping.
This issue represents the creation of some sort of process manager for Ambition applications, running the application in a safe environment and allowing some sort of handler to run if something goes terribly wrong. It's entirely possible that the "Engine" should reside here instead of in the application itself.
This needs to be fleshed out further.
The current layout of an Ambition application doesn't actually make sense, and it's due to some experimentation with how to handle bad code and segmentation faults. The
ambition runandambition monitorcommands are simple runners that allow an application to stay running when the developer makes a mistake, but they don't actually do any failure handling or trapping.This issue represents the creation of some sort of process manager for Ambition applications, running the application in a safe environment and allowing some sort of handler to run if something goes terribly wrong. It's entirely possible that the "Engine" should reside here instead of in the application itself.