John McNally and I were noticing that Include's use of ContentResource could be streamy, but because ContentResource provides its data as a String rather than as a Reader or InputStream, that the result is non-streamy.
Geir, Jason, any quick pointers on how I could address this in a safe and preferably backward-compatible fashion (see Include.renderOutput() for a point of reference)? How about a new Resource which is similar to ContentResource but which returns a Reader with its getData() method, rather than a String object? This seems like it would fix the streaminess problem, but I worry about other unforseen gotchas which it may introduce. - Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
