Open pizthewiz opened 9 years ago
GET
/ctrl/card could respond with 204 if present and 404 if notPOST
/ctrl/card/format/An RPC based api would probably be better suited to this kinda of work
I would second this issue and would also favour a RESTful API.
Generally the API called out in http.md is not RESTful;
GET
s are used when deleting and adding resources - is this due to the limited HTTP verb support in the E1 hardware or would you be open to a proposal for a RESTful HTTP API?A couple examples off the top of my head:
GET
/DCIM/100MEDIA/EYED0001.MOV?act=rm could be aDELETE
GET
/ctrl/session?action=quit, /ctrl/shutdown, /ctrl/reboot, /datetime?date={YYYY-MM-DD}&time={hh:mm:ss}, /ctrl/still?action={cap}, _/ctrl/mode?action=topb … could be aPOST
GET
/ctrl/mode?action=query could be query-less