| Key: |
SES-34
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Jeen Broekstra
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
Sesame
Created: 14/Apr/04 11:27 AM
Updated: 07/Feb/05 12:29 PM
|
|
| Component/s: |
SeRQL,
Extract
|
| Affects Version/s: |
1.0
|
| Fix Version/s: |
None
|
|
The current approach for reporting errors that occur during processing of a request is fundamentally flawed. In the case of RDF graphs that are serialized as RDF/XML, errors that occur during evaluation are reported as XML comments.
This is done because we can not use HTTP error codes at this point: the server is already sending data to the client, so the response is already committed.
To fix, the server should build and serialize the result set completely before sending it to the client. This way, HTTP error codes can be used at any point to indicate problems.
|
|
Good place to look for solutions is the upcoming SPARQL protocol WD
|
|
Error reporting in streaming RDF/XML graph results over HTTP