In a new post today Raphael Stolt shows you how to use MongoHq, a cloud-based hosting service, to host a Zend Framework application that uses the MongoDb as a backend. The tutorial focuses on the bootstrapping process to make the framework play nicely with its hosting environment.

Since [MongoHq] went live a few weeks ago I signed up for the small plan and started to successfully re-thinker with it in an exploratory Zend Framework based application. [...] Therefore the following post will show how to bootstrap such an instance into a Zend Framework based application and how to use it from there in some simple scenarios like storing data coming from a Zend_Form into a designated collection and vice versa fetching it from there.

He shows how to create a new resource to make the MongoDb connection available through the entire application, to be used as needed. The resource creates the MongoDb connection based on the options from the config file and catches any exceptions that might happen along the way. As mentioned, he also includes a Zend_Form example that stores some proposal information in a collection in the database.

On the Zend Developer Zone there's a recent post from Kevin Schroder (a Tech Evangelist at Zend) about the MVC request lifecycle for the Zend Framework every time an application runs.

When I have done training for Zend Framework, one of the things that mystifies students to some extent is the whole plugin architecture and where things can go. There has been several articles written about it, but they tend to use code to describe it. [...] I had found that when I drew out the request lifecycle that it helped the students understand it better.

His diagram (seen here) lays out the full execution relationship for the request structure including where plugins, action helpers and controllers fit in the mix. He also describes it in more detail, mentioning some of the variations that could happen along the way.

In response to one of the constant claims about the Zend Framwork - that it's large and bloated - Juozas Kaziukenas tries to dispel three things that people use to reinforce this belief.

Zend Framework is always considered as being the slow/bloated one. I don't think this is right, so I decided to prove that it's not correct and in fact ZF is as good as other frameworks are. This post doesn't cover any benchmarks though; this is more like a architecture review and some misconceptions disproof.

He counters the following with a bit of logic that makes the points a bit more shaky than they first seem:

• Large installation footprint
• Unnecessary features
• Use more system resources

If you're still not convinced, he offers two other tips to help streamline your Zend Framework install - profiling to find the bottlenecks and using Zend_Application sparingly as it can be a bit of a resource problem.

A recent tutorial (screencast) has been posted to the ZendCasts.com site looking at creating custom Zend_Form elements when you need something more than just the usual, simple elements.

This video should help you build your own composite Zend_Form element. We'll be building a phone element. The phone element will have 3 textboxes, one for geographic location, area code and local code. In the following videos will add a custom cell phone validator and some ajax validation.

You can grab a copy of the source if you'd like to follow along or you can just look around the repository to find the source for this and other great lessons from the site.

If you've been looking for a good way to get introduced to the latest version of the Zend Framework but didn't know where to start, you might grab a spot in this upcoming webinar from Zend about the Zend Framework 1.10.

Zend Framework 1.10 sports a ton of new features, as well as completely revamped online documentation. In this webinar, Matthew Weier O'Phinney, Framework Project Lead, and Ralph Schindler, Zend Framework Software Engineer, will present a synopsis of the new features, discuss the new online documentation system and how it's built, and answer your questions about the new release.

The webinar will be happening this coming Wednesday, March 17th, at 9am PST and will be happening via WebEx. Matthew Weier O'Phinney and Ralph Schindler will be talk about the new features, current functionality that was enhanced and will answer your burning questions. To reserve your spot, head over to the registration page and enter your info.

Matthew Weier O'Phinney as a new post to his blog today looking at a few "do's" and "dont's" when it comes to working with module boostraps in your Zend Framework applications - an apparently somewhat confusing topic for several developers out there.

In Zend Framework 1.8.0, we added Zend_Application, which is intended to (a) formalize the bootstrapping process, and (b) make it re-usable. One aspect of it was to allow bootstrapping of individual application modules -- which are discrete collections of controllers, views, and models.

He talks briefly about why module boostraps are run on every request (getting into some detail on Zend_Application), how you can properly set up your boostrapping process and how you can use plugins to initialize only the things you might need and, as he openly admits, that there's just not a really good way to handle this sort of module funcionality.

Joseph Crawford has a new post to his blog today with a look at his use of the Zend_Rest_Controller and Zend_Rest_Route components of the Zend Framework to create a simple REST service.

You might be asking yourself why do I have to use both components, why is it not rolled into one nice component. The answer is really basic and if you look at the source code for the Zend_Rest_Controller you will see that it is solely an abstract class that defines the methods required for use with the Zend_Rest_Route.

He includes the code to add to your bootstrap file to get the routing working and a sample controller (MyController) that extends the Zend_Rest_Controller and sets up some basic actions - get, put, post and delete. He does mention one issue he's coming across in a feature he's wanting to add - putting the version number of the API in the URL for easier separation.

On DZone.com today there's a new interview by Lyndsey Clevesy with Jason Gilmore looking at the Zend Framework and some of the general things to expect in coming versions.

This week's DZone Refcard is about Getting Started with the Zend Framework. The card introduces you to the basics of the Zend Framework and sets you on the path to creating your first project. I met the author, Jason Gilmore, to find out more about the topic.

They talk about some of what the framework currently has to offer developers, what kind of involvement he's had with it, who it supports as far as advanced PHP features and what's to come in version 2.0. The Zend Framework RefCard mentioned can be viewed or downloaded here - a six-page quick reference for some of the more common Zend Framework tasks.

Continuing on from his previous articles on working with REST in Zend Framework applications (and making the endpoints for a web service) Matthew Weier O'Phinney has a new tutorial with the next logical step in the series, automatically responding to different content types in your application based on the content-type the client sends.

There's no reason you can't re-use your RESTful web service to support multiple formats. Zend Framework and PHP have plenty of tools to assist you in responding to different format requests, so don't limit yourself. With a small amount of work, you can make your controllers format agnostic, and ensure that you respond appropriately to different requests.

He talks about concerns you'll have to worry about when developing your service - grabbing teh raw input instead of the POST values (since most requests will be rawly POSTed) and what to pass that message to to decode it properly. In his example the Zend_Json and Zend_Config_Xml components make it simpler to handle the info and some code to get the results back into your script.

There's also some code for the other side of things - building the response and pushing it out to the correct views depending on the request content type, action and information.

On the Zend Developer Zone there's a new tutorial for those using the Zend Framework (and more specifically the Zend_Auth component) on a way that you can prevent identity theft in validating your users.

As I am building my applications, I always try to improve the code I write in some way. Today I thought about the security issues of any PHP application that uses an authenticating system. [...] There is one particular issue that bugged me for some time. The Identity theft - Broken account and session management issue. Why can one so easily still my session id cookie and suddenly gain access to my account in one particular web application?

He shares a class he's developed as a guideline to help your application automatically test to ensure that the information being given by the user is valid. It checks a security level and validates against the user agent and remote IP of the user to ensure they match. These two criteria might not always be the best choices, but it gives you a push in the right direction.

Code is also included to show how to integrate it into your Zend Framework application by loading it into your base controller and using the "hasIdentity" and "hasSecureIdentity" methods to check the user's credentials.