a14c1775b1
api: allow a start time (&start=...), end time (&end=...) and
...
resolution(&resolution=...) to be specified
Either an interval or start parameter is required, while the end
parameter is optional when start is specified. Start and end should both
be specified in unix time format. Resolution is in seconds and should be
one of [60 | 900 | 86400 | 604800] meaning [minute | 15min | day | week]
resolution respectively.
The [time, power] pairs returned by the api will be aligned to multiples
of the specified resolution, or maximum resolution available for the
requested time interval.
2010-05-22 13:21:31 +02:00
fdd5363cf7
api: allow a start/end unix time to be specified instead of an interval
2010-05-21 16:25:01 +02:00
c69f4d65c8
api: include checking of version information in header or query string
2010-04-28 00:08:41 +02:00
54c151c4a5
api: rename check_factor into check_unit
2010-04-27 23:47:01 +02:00
a1d81946f3
api: rename input validation functions
2010-04-27 23:23:27 +02:00
606efd7c79
api: allow the token to be submitted either in the request header or as part of the query string
2010-04-27 23:14:30 +02:00
ea9f713f90
api: night values were not taken from the proper database since we were checking against path_info instead of get_qs_value
2010-04-27 14:22:25 +02:00
e081a2e95c
api: implement a jsonp callback parameter
2010-04-24 01:20:47 +02:00
155f2bfef9
api: introduces token-based authentication
2010-03-14 20:31:10 +00:00
a53fa50f80
api: use pattern matching in to_json arguments
2010-03-14 14:12:35 +00:00
4a5e939acc
api: use record instead of tuple to pass around State
2010-03-14 13:47:28 +00:00
3de06ee609
api: initial import of mysql driver in webmachine
2010-03-13 13:00:51 +00:00
6d907016dd
initial import of webmachine-based api
2010-02-25 17:45:11 +00:00
Bart Van Der Meerssche