edge cases

If you were to use our framework right now, you would probably have to add support for custom error messages.

Right now, we have 404 and 500 error support but the responses are hardcoded in the framework itself. Making them customizable is easy enough though: dispatch a new event and listen to it.

Doing it right means that the listener has to call a regular controller. But what if the error controller throws an exception?

You will end up in an infinite loop. There should be an easier way, right?

Dealing with character sets and encodings is tough. As long as you're dealing only with English texts you in a luxury situation and can mix utf-8 and iso-8859-1 encoded texts and most (all?) of your tests will work.

Some of your users, like me, with strange names ("Schlüter") will be annoyed as your application breaks them ("Schlüter"), but these will be edge cases.

There are bigger issues with mixing encodings but that's not what I wanted to tell now.

One of the most significant changes in the new uTorrent is uTP, the ‘micro transfer protocol’.

UTP is a new and improved implementation of the BitTorrent protocol which is designed to be more network-friendly than its predecessor.

In this new post from Abhinav Singh on how to use file locking to keep your cron jobs from trying to use the same resources.