Hi Simon,
What a nuisance. It's not, as far as I know, illegal, but it is a
rather odd interpretation of HTTP POST for remote operations.
Not sending Accept is because it's a POST which does not need to
return anything. conneg for an HTML page is find but it's not conneg if
it returns it
Ok, i will ask Dydra first whether this kind of conneg is a bug or a
feature.
2012/12/6 Rob Vesse rve...@yarcdata.com
My two cents:
In my experience of writing a HTTP connector for Dydra for dotNetRDF it
proved to be a pretty awful implementation of HTTP conneg and SPARQL
protocols in
If Jena would be consistent in its HTTP handling and use an
established API such as JAX-RS, things could be much easier.
Martynas
graphity.org
On Thu, Dec 6, 2012 at 6:04 PM, Rob Vesse rve...@yarcdata.com wrote:
My two cents:
In my experience of writing a HTTP connector for Dydra for
On 06/12/12 20:03, Martynas Jusevičius wrote:
If Jena would be consistent in its HTTP handling and use an
established API such as JAX-RS, things could be much easier.
Could you explain that a bit more so we can see what can be improved (or
submit a patch)? Do you have specific suggestions?
On 12/6/12 12:31 PM, Andy Seaborne a...@apache.org wrote:
On 06/12/12 20:03, Martynas Jusevičius wrote:
If Jena would be consistent in its HTTP handling and use an
established API such as JAX-RS, things could be much easier.
Could you explain that a bit more so we can see what can be improved
Andy, we've been through this already:
http://mail-archives.eu.apache.org/mod_mbox/jena-users/201202.mbox/%3ccae35vmzpcczxswt37etsb_5bzw6qgv-uufphy8bx6ssh4u9...@mail.gmail.com%3E
OK, maybe I should say JAX-RS and Jersey as its implementation, which
also includes the client.
JAX-RS allows not
On Thu, Dec 6, 2012 at 3:36 PM, Rob Vesse rve...@yarcdata.com wrote:
On 12/6/12 12:31 PM, Andy Seaborne a...@apache.org wrote:
On 06/12/12 20:03, Martynas Jusevičius wrote:
If Jena would be consistent in its HTTP handling and use an
established API such as JAX-RS, things could be much easier.
On 06/12/12 20:48, Martynas Jusevičius wrote:
Andy, we've been through this already:
http://mail-archives.eu.apache.org/mod_mbox/jena-users/201202.mbox/%3ccae35vmzpcczxswt37etsb_5bzw6qgv-uufphy8bx6ssh4u9...@mail.gmail.com%3E
Have you looked at Stephen's work on jena-client?
OK, maybe I
On 06/12/12 20:49, Stephen Allen wrote:
However perhaps we should be ensuring that everywhere that does anything
HTTP uses the Apache HttpClient as a point of standardization and provide
ways to better expose that up to users to add custom configuration?
On the way to that : the idea of
On 03/12/12 12:44, Simon Gábor wrote:
Hi All,
According to the SPARQL Update protocol recommendation:
The response body of a successful update request is implementation
defined. Implementations *may* use HTTP content negotiation to provide both
human-readable and machine-processable information
I have a system that does conneg and returns different bodies for
SELECT statements, we don't support UPDATE but if we did I suspect
that we would also return different bodies in that case.
On Wed, Dec 5, 2012 at 11:52 AM, Andy Seaborne a...@apache.org wrote:
On 03/12/12 12:44, Simon Gábor
On 05/12/12 12:22, Claude Warren wrote:
I have a system that does conneg and returns different bodies for
SELECT statements, we don't support UPDATE but if we did I suspect
that we would also return different bodies in that case.
Slightly different case - Fuseki does conneg for query and for
Hi Andy,
I am trying to use Dydra (http://dydra.com/). It requires to send Accept
header, otherwise it returns with a full HTML webpage (with Dydra's online
query tool on it). For update commands it is happy with just an Accept: */*
then returns 200 and a simple boolean SPARQL XML result.
13 matches
Mail list logo
