On 04/12/13 14:14, Rob Vesse (JIRA) wrote:
It would also be useful if the various locator implementations took compression
into account when opening input streams
I would not built that in at the lowest level - LocatorFile should set
an appropriate content type for the compressed stream. The caller may
just want to do byte-copy of a stream, leaving it compressed.
I'm fairly sure if you asked ARQ to open a {{foo.nt.gz}} file it would just
open a raw input stream and then the reading would fail.
If true, surely the fix is to make ARQ go through RIOT which does handle
at least .gz.
Andy