Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
In some cases (like the webloader example), long-running processes need to be started, monitored and stopped.
The webloader implements this in a naive way, it might be useful to have a more generic facility for this: a service that would:
1) Start a script or servlet, probably passing it a fake request object that gives access to parameters and output but is not a real HTTP request
2) Display a status page where currently running jobs can be monitored, and stopped if desired
3) Collect the output of such jobs in the repository and give access to it via a simple monitoring interface
The output of long-running jobs could be structured using html conventions (like <div class="status">running step 3 of 12</div>) to create overview displays of all currently running jobs.
This is just an idea for now, I'm not going to work on this right away, but it's probably good to keep in our wishlist.
Attachments
Issue Links
- is blocked by
-
SLING-1596 Reduce coupling between RequestData and SlingHttpServletRequestImpl
- Resolved
- is related to
-
SLING-2327 Visible TODOs in the background servlets console
- Resolved
- relates to
-
SLING-1603 SlingServlet service
- Closed