API endpoints

[ArthurHoaro]

As discussed in #3 we have 2 ways to handle parameters:

Method	Endpoint
DELETE	?do=api&q=/links/Shsmbw
POST	?do=api&q=/links
GET	?do=api&q=/links&limit=20

or

Method	Endpoint
DELETE	?do=api&request=links&param=Shsmbw
POST	?do=api&request=links
GET	?do=api&request=links&limit=20

Optionally we can add URL rewriting for cleaner URL.

The first one requires a bit of work to handle parameters properly, while the second one makes URL rewriting more complex.

EDIT: parameter names are also debatable, but won't be used client side if we add URL rewriting.
EDIT BIS: I forgot the API version, but you get the idea.

[ArthurHoaro]

My vote goes to the first method with URL rewriting.

• URL rewriting from the beginning to avoid client using previous format the day we add clean URL.
• The first method because handling slightly complex parameter a easier than writing complex URL rewriting in multiple web server configuration syntax.

This means that we would have

Method	Endpoint	Real URL
DELETE	/api/v1/links/Shsmbw	?do=api&version=1&q=/links/Shsmbw
POST	/api/v1/links/	?do=api&version=1&q=/links
GET	/api/v1/links?limit=20	?do=api&version=1&q=/links&limit=20

[ArthurHoaro]

URL rewriting is handled by Slim.