[
https://issues.apache.org/jira/browse/SLING-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-9364.
---------------------------------
Resolution: Fixed
Fixed in [commit
6c5b2ed|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker/commit/6c5b2ed].
> Implement lazy response writer
> ------------------------------
>
> Key: SLING-9364
> URL: https://issues.apache.org/jira/browse/SLING-9364
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting Bundle Tracker 0.1.0
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Historically, the {{org.apache.sling.scripting.core.ScriptHelper}}
> implementation relied on an on-demand response data writer, which allowed
> scripts to open writers or streams. If the scripting opens a writer directly,
> it will not allow scripts to stream data at a later point. Since a lot of the
> available Sling scripts rely on this behaviour, the Scripting Bundle Tracker
> should provide a similar implementation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
