[ https://issues.apache.org/jira/browse/SLING-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-550. ------------------------------------ Resolution: Won't Fix > Support for background servlets > ------------------------------- > > Key: SLING-550 > URL: https://issues.apache.org/jira/browse/SLING-550 > Project: Sling > Issue Type: Improvement > Components: Extensions > Reporter: Bertrand Delacretaz > Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)