| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
Get rid of the complicated dbfp_status structure and use plain old
return codes. This leads to a cleaner interface and fixes the problem
with unsufficient error handling introduced with 1648e81. The drawback
is that the details of curl and expat errors are hidden from the user,
but this can be adressed later.
|
| |
|
|
|
| |
dbfp_query_location_name will not be the only function that needs curl,
but it is not necessary to initialize and cleanup curl more than once.
|
| |
|
|
|
|
| |
The old code returned a successful status, but does not set the result
values if there are no results. This patch changes the error handling
so that the results are always set if no error occured.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The function dbfp_query_location_name performs the location.name query
and returns a list of all stations that match the search term. The
implementation has two flaws: there is no URL encoding, and
malformatted query results will not lead to a meaningful error message.
There are two new test cases: basic tests some basic functionality, as
setting the API key and accessing the API. location adds a simple test
for the location.name query.
|
| |
|
