Rest
Rest copied to clipboard
Respect
Thin controller for RESTful applications
What if routines were events? Since they At first purely cosmetic refactor imploring the use of a Dispatcher pattern instead of Abstract Routine doing the work. ``` php
@alganet on #php-respect 20120711 dunno yet I'd like to see $router->any('/messages/*')->linkTo($mailboxRoute); something between the route objects but I'm not sure about the API
We currently don't have real unit tests, our tests are more functional/BBDish. I'm gonna write the proper units and keep the old tests as legacy, already started!
This feature is dependent on the implementation of the [ETag](http://pretty-rfc.herokuapp.com/RFC2616#header.etag) see #40 Implement capabilities required for conditional requests: - [If-Match](http://pretty-rfc.herokuapp.com/RFC2616#header.if-match), - [If-Modified-Since](http://pretty-rfc.herokuapp.com/RFC2616#header.if-modified-since), - [If-None-Match](http://pretty-rfc.herokuapp.com/RFC2616#header.if-none-match), - [If-Range](http://pretty-rfc.herokuapp.com/RFC2616#header.if-range), - [If-Unmodified-Since](http://pretty-rfc.herokuapp.com/RFC2616#header.if-unmodified-since) and -...
This is a topic I've been burning to raise but there are still features required that takes a higher priority than this. Since the RESTful API architecture involves extensive CACHE...
A routine that receives an IP address and must return `false` if not being rate-limited or an integer with number of seconds to retry. Implement 429 status code as well.
Convert PHP errors and uncaught exceptions into 500 status codes. 408 may be used for timeout if we could figure out a way to calculate max_execution_time.
ETag support
Automatic generation by MD5ing the content. Custom logic can be implemented separately.
Maybe the user may need to provide a closure for that, we can pass him the choices.