Comments on: AMF,XMLRPC,JSON,REST Zend Web Services Tutorial

By: Albulescu Cosmin

Albulescu Cosmin — Thu, 06 Oct 2011 08:09:48 +0000

Hi, very nice post. Very usefull

By: Joey

Joey — Thu, 19 May 2011 18:44:00 +0000

Thanks, they should be back up now.

By: DiegoAlberto

DiegoAlberto — Thu, 19 May 2011 18:34:28 +0000

Dude your examples links are not working.

By: Joey Rivera

Joey Rivera — Fri, 27 Mar 2009 13:32:41 +0000

Matthew, thanks for the great feedback. I completely missed Zend_Json_Server when looking at the documentation and I’ll look into it. I also agree with the redundancy aspect of the way I’ve created these services. For a real project I would most likely do as you mentioned and keep the project more lightweight.

By: Matthew Weier O'Phinney

Matthew Weier O'Phinney — Thu, 26 Mar 2009 21:28:48 +0000

You can actually simplify your JSON example by using either the ContextSwitch or AjaxContext action helper; by default, the JSON context takes all variables assigned to the view and simply returns a JSON representation of them. You might also want to experiment with the JSON-RPC server (Zend_Json_Server) as a more standardized format for handling JSON requests.

Also, one note on architecture here. While many people like to intercept all calls with the MVC, with services this doesn’t make a lot of sense. The server classes act as your controllers, and the protocol they serve dictates the view; as such, using the MVC is redundant — and also adds quite a bit of overhead. I typically create a service script for each protocol I want to provide a service for, and use rewrite rules to map to them (which allows me to move them around in my architecture later if need be).

Overall, though, it’s a nice demonstration of how all of our server classes provide a common API — allowing you to re-use your service classes/domain models for a variety of protocols.