Hi Andreas, > No, basically the code would take an OMElement and return a Reader > that represents the text content of that element. It would take care > of doing this in an optimal way (constant memory usage and minimal > usage of intermediate buffers), i.e. it would provide the same > functionality than new StringReader(omElement.getText()), but without > loading the entire data into memory. We already do something like this > in the PlainTextFormatter, but here the idea is to encapsulate that > nicely behind a Reader implementation. Note that this is not at all > transport specific and would work with any OMElement.
+1 sounds very useful
