This is the second of a series of articles discussing ongoing developments with AmfPHP. The idea is to give the community the chance to give feedback before a final release is made, and of course simply to let people know what is going on. The first is here. Get the download here
One of the key selling points of the AMF format is that you can use it to transmit typed objects. Previous versions of AmfPHP had a plugin, AmfphpCustomClassConverter, whose responsibility was to manage these typed objects. It did its job reasonably well, but had some limitations which have been adressed in its successor.
If you use AmfPHP to transfer large amounts of typed data, you should see some significant performance increases. This is especially for Baguette AMF users. One tester was sending 600 kbytes of nested objects, and was having performance issues: Some of his requests would take 15 seconds to process. He went from 15 seconds to 5 seconds per request when installing Baguette AMF, then down to 1 second per request with this update.
This only works for AMF(not JSON), and should have a significant impact if you’re sending large quantities of data, even more so if the data contains nested typed objects. The technicalities are beyond the scope of this article, but might be discussed elsewhere.
Better developer experience
Vo conversion is optional. As typing is not enforced in PHP, it makes sense to do without it completely and just use anonymous objects with « _explicitType » marked to whatever type you want to send back to your client. Hence by default the Vo Converter’s default behavior when it doesn’t find a class with a certain type is just to give you an anonymous object.
This is fine for production, but when developing, it would be nice to be informed when a class is missing. So a new feature is the « enforceConversion » flag. If set to true, an exception is thrown when a VO class is not found. This exception contains information about what was sought, and the various possible paths where it could be found, so be sure to remove it for production.
It is now possible to use namespaces in your Value Objects.
Here is a snippet to show how you would configure the Vo Converter. the first entry in the array is the path to the folder, and the second is for the root namespace, ‘NVo’. So a « \NVo\MyVO » class in « NamespaceVo/MyVO.php » can be sent with a client(explicit) type « MyVO ».
$voFolders = array();
//add the folder with the namespace. 1st comes the pass, 2nd comes the namespace root.
$voFolders = array(dirname(__FILE__) . '/NamespaceVo/', 'NVo');
$config->pluginsConfig['AmfphpVoConverter'] = array('voFolders' => $voFolders);
Note that this is the same system as for service folders.
Nobody knew what the custom class converter did without looking it up. It’s now called Vo Converter.
- The back office tells you what version of AmfPHP you’re running and whether you’re up to date. A mini RSS reader is also tucked away so that you can get AmfPHP news.
- You can choose to make calls from the Service Browser either in JSON or AMF.
- Put an @amfphpHide tag in your service or method’s comments, and it won’t appear in the back office
- The service browser now truncates data when it’s too much to display. This avoids you killing your browser when you’ve loaded big data in the service browser.
- The AmfPHPErrorHandler has been enhanced so that it does not throw exception for which reporting has been disabled.
- Yes we’re still working on the styling of the back office. So here’s yet another look, tell us what you think!
- A guide to migrating your config can be found here.
- Thanks Tommie for all the testing and feedback.
- Thanks Dan Franklin for the AmfphpErrorHandler suggestion and code