Post-processing for a bad inbound responses
GNU GPL v2+
- Since
- 2.0
- Author
- Markus Krötzsch
-
mwjames
◆ __construct()
SMW\SPARQLStore\HttpResponseErrorMapper::__construct |
( |
HttpRequest |
$httpRequest | ) |
|
◆ mapErrorResponse()
SMW\SPARQLStore\HttpResponseErrorMapper::mapErrorResponse |
( |
|
$endpoint, |
|
|
|
$sparql |
|
) |
| |
Either throw a suitable exception or fall through if the error should be handled gracefully. It is attempted to throw exceptions for all errors that can generally be prevented by proper coding or configuration (e.g. query syntax errors), and to be silent on all errors that might be caused by network issues or temporary overloading of the server. In this case, calling methods rather return something that helps to make the best out of the situation.
- Since
- 2.0
- Parameters
-
$endpoint | string URL of endpoint that was used |
$sparql | string query that caused the problem |
- Exceptions
-
Exception | |
SparqlDatabaseException | |
The documentation for this class was generated from the following file:
- HttpResponseErrorMapper.php