[
https://issues.apache.org/jira/browse/SLING-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239405#comment-13239405
]
Ben Peter commented on SLING-2449:
----------------------------------
It would probably make sense to support a larger part of the
SlingHttpServletResponse interface, esp. adding headers and cookies, but this
goes towards a full JCR-based response serialization - that should perhaps not
be locked in with the background jobs but be available for other purposes as
well. From a first scan, nothing of the kind is available yet.
I briefly scanned for header and cookie serialization to JCR but didn't see
anything.
> background servlets: enable tracking of user, status-code, content-type,
> length and encoding
> --------------------------------------------------------------------------------------------
>
> Key: SLING-2449
> URL: https://issues.apache.org/jira/browse/SLING-2449
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Ben Peter
> Labels: patch
> Attachments:
> SLING-2449_background_servlets__enable_tracking_of_user,_status-code,_content-type,_length.patch
>
>
> Enable background jobs to store the user on whose behalf the request was
> backgrounded
> Enable background job to store the following data from the result of the
> backgrounded request:
> * HTTP Status
> * Status Message
> * Content-Type
> * Content-Length
> * Character-Encoding
> Change {{JobStreamServlet}} to return the stored data appropriately
> Change {{JobConsolePlugin}} to display information on User, Status Code and
> Message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
