You should see that without the ProxyPassReverse line, an application redirect to “test.jsp” will become a HTTP redirect to “http://www.example.com/jspdir/test.jsp”. The ProxyPassReverse line will translate that redirect to the correct “http://www.example.com/test.jsp”.

HTH

Simon.

su -
rm /var/lib/nfs/rmtab
reboot

NFS started instantaneously rather than taking several minutes.

Thanks,
Chris.

This structure actually helps avoid the raster order problem for DC prediction, because you can undo the DC prediction after decoding just the DC coefficients, i.e., on 1/64th of the final image data, which often fits entirely in cache (at 640×480 it’s less than 16k of data).

The loop filter problem can similarly be handled by applying it (with a one block row delay) after each super block row is decoded. This requires slightly more cache (just under 64k of image data at 640×480, plus additional overhead for the coefficients that were decoded), but should still fit well within the 256K L2 cache on your DSP.

The theora-exp decoder does both these things, to good effect. The spec describes everything as separate processes for conceptual simplicity, but to get good preformance they really need to be pipelined.

For the loop filter at larger resolutions, you could (if you’re careful about it), process 3/4 of each superblock (with a one block column delay) immediately after decoding it, without waiting for the entire row to finish. Then you only need to cache one row of block data between superblock rows.