Stablr, the proposed name, will be the main gateway for it's users. People will post to Stablr, which will then (when it can) forward it to Twitter. If a Stablr users posts to Twitter directly, the message will be retrieved and replicated on Stablr. Responses to posts, direct messages, and tweets from friends of Stablr users would also be replicated.

He's already seen some great response from the community with offers to help and has taken it to the next level by coming up with a five-page document detailing the plans behind the project (using things like caching, an Access database and Jabber integration).

I often use this when implementing a simple login screen for a password protected section of my application. In a Zend Framework application you can implement a preDispatch() function in a Zend_Controller_Action which will run before an action is dispatched. This lets you setup your filter to check to see if the visitor is logged in or not. If the visitor is not logged in, you can redirect them to the login screen of your application.

He includes example code to show its usefulness - checking to see two things: is a user is logged in and to see if they're allowed to use a certain resource.