incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-210) Make QueryEngineHttp more configurable
Date Mon, 13 Feb 2012 02:40:59 GMT


Hudson commented on JENA-210:

Integrated in Jena_ARQ #452 (See [])
    JENA-210 patch applied with fixes and changes as detailed in the JIRA. (Revision 1243160)

     Result = SUCCESS
andy : 
Files : 
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/

> Make QueryEngineHttp more configurable
> --------------------------------------
>                 Key: JENA-210
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: ARQ
>    Affects Versions: ARQ 2.9.0
>            Reporter: Rob Vesse
>              Labels: http, query, results, sparql
>             Fix For: ARQ 2.9.1
>         Attachments: HttpQueryEnhancements.patch
> The current QueryEngineHttp is somewhat limited in that the Accept header is hardcoded
to SPARQL Results XML or RDF/XML depending on the usage of the engine and there are a number
of other features lacking including timeouts and support for requesting and reading compressed
> The submitted patch here adds the following features:
> 1 - Configurable Content Type support
> A QueryEngineHttp instance can be configured to request different content types as required
by the users.  For CONSTRUCT/DESCRIBE whether the requested content type is valid is verified
using RIOT and the parser for reading responses into models automatically selected.  For ASK/SELECT
the supported content types are defined in hard-coded lists and the parser selected via if
> In the future it is envisaged that ASK/SELECT supported format detection could be improved
by wiring into whatever new machinery around handling result formats that ARQ/RIOT eventually
> 2 - Configuration Timeouts
> Support for configuring Connection and Read Timeouts for queries
> 3 - GZip and Deflate Compression Support
> Support for specifying that the client will allow GZip/Deflate encoded content to be
sent to it and for ensuring that the returned InputStream gets appropriately wrapped so the
content is decompressed as read

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message