I've begun integrated ETag's into a Laravel 4 API application. I've started by implementing Conditonal GETs.

I've been scouring the internet for good information on setting up user and group permissions for Apache. I'll link some resources on the bottom here, but here's what I found:

@fideloper the latter and hope I don't have to use reflection to mock a private/protected method

February 26, 2013

I last wrote about ETags in context of Conditional GETs, which allow a server to see if a resource has been modified since the last time a client checked. If it has not been modified, the server can return a 304 Not Modified response.

My curiosity about ETags (Entity Tags) was first piqued when reading over Github's API documentation. Looking into them, I saw that there explanation often pointed to them as a "cacheing" mechanism.

In looking to build a RESTful API, an important consideration is how to handle errors. Most errors are displayed to users in HTML, as these are web applications. However, API's need some special care.

Here's how to get started really quickly with Laravel 4. Updated since Laravel 4's official release!

If you make judicious use of IoC containers (and Dependency Injection), you'll likely end up with lots of Bindings, some of which may look like:

I like to create my own library for any application. Similarly, I like keeping the "models" directory clean - I only add Laravel classes (Usually Eloquent instances) inside of the "model" folder.

Laravel encapsulates HTTP requests and responses within PHP objects. As you likely know, the HTTP core of Laravel revolves around Symfony's HTTPFoundation component.

Laravel uses Exceptions for error handling. This includes both HTTP error codes and application (run-time) errors.

Quick (and dirty) tip:

For desktop, I love native apps - They run smoothly, they have great OS integrations, and they often get away with a polish impossible on the web.

Ubuntu has an OS targeted for smart phones. After my initial excitement at the prospect of having an OS I could really nerd out on (Really hoping for a Terminal app), I realized one thing: I don't use any of Ubuntu's graphical tools.

Last week, during our break, we switched from a hosted Exchange service to Google Enterprise. The main driver to change was lack of space - some of us have emails going back 7 years and have accrued many gigabytes of data. Adding more available space was getting too costly.