Changeset 379d1b5e9c52e9ac879b4baefb04e23f4cdd2106 adds basic error handling logic for RDF::WriterError exceptions, improving present-time usability of the gem on Heroku given that the RDF::Raptor gem does not yet work in that hosting environment (soon to change for the better, hopefully).
Since 0.1.2, if an RDF::WriterError is caught when attempting to serve a negotiated serialization format, we now output a 406 Not Acceptable response. This ought to be further enhanced so that we will attempt serializing into the next most-preferred format (if any) indicated by the client.
Changeset 379d1b5e9c52e9ac879b4baefb04e23f4cdd2106 adds basic error handling logic for
RDF::WriterErrorexceptions, improving present-time usability of the gem on Heroku given that the RDF::Raptor gem does not yet work in that hosting environment (soon to change for the better, hopefully).Since 0.1.2, if an
RDF::WriterErroris caught when attempting to serve a negotiated serialization format, we now output a406 Not Acceptableresponse. This ought to be further enhanced so that we will attempt serializing into the next most-preferred format (if any) indicated by the client.