19 Dec
2012
19 Dec
'12
7:07 p.m.
On 12/17/2012 12:31 PM, Paul Libbrecht wrote:
Hello XWiki experts,
I'm implementing OAI-PMH, a service infrastructure to aggregate digital library
items.
I do so with a few velocity pages and a groovy page. I'll happily share it.
At first, I did not implement the "resumption" flow-control, which allows a
big search list to be paged in several requests as I expected the output of my velocity
script to trigger a buffer-full and start delivering the packets down the line.
But this fails, nothing comes before it's finished.
And indeed, I receive a content-length header... so there is buffering happening
somewhere.
Do I have a possibility to disable velocity output buffering?
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.
--
Sergiu Dumitriu
http://purl.org/net/sergiu