Matt Sergeant wrote: > > Also note this won't work with -async properly. I'll have a look how it > can be made to work asynchronously (you need to follow the respond > style in the rest of the code).
For some reason, I thought I looked at the rest of the code and
convinced myself it would, because I was expecting the respond style.
It should probably be wrapped in a if (!async) {}
For the short term, i've committed a change to my tree to document its
brokenness.
