> It's not Velocity that's buffering, it's the whole rendering engine that > does that. Velocity itself is just one of the steps through which > document content passes, and each step outputs everything in a buffer > which is later flushed down the socket after every rendering step is > finished. > > At least that's what's happening if you use the rendering engine to > "run" code from wiki documents.
Is there any way to disable buffering at each of the steps? I'm thinking this may have a performance impact. However, for my case, implementing OAI-PMH, I've solved it by using the "query resumption" that the protocol offers. paul _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
