AMFPHP uses flash remoting whereas PHPObject uses PHP's built in serializer
methods for passing complex objects. It's a matter of preference since both
are quite speedy. AMFPHP allows you to send back custom classes from PHP -
I'm not sure PHPObject does this.
You could also look at Sephiroth's Serializer Class for a stripped down,
lightweight way of passing objects. PHPObject might even use this class
since it now appears as a sourceforge project.
www.sephiroth.it
Stephen
> Hi
>
[quoted text clipped - 8 lines]
>
> Ernesto
boyHowdy - 23 Sep 2004 23:20 GMT
I've had mixed results with PHPObject. The use of it in aScript is a little
rough. It doesn't try really to mimic Flash Remoting. PHPObject is a _very_
basic way to pass (or more accurately, pull) instances of classes into aScript
and use them pretty much as-is.
AMFPHP is the obvious choice if what you want is the features of Flash
Remoting (and its components) but with PHP. It's class library (on which it
runs) is large and complex.
Having now upgraded my server to PHP5 and have a brand spankin' new mySQL
4.1.x server to match. PHP/mySQL has just gotten a _lot_ easier with these 2
_major_ updates. The trick is how to get AMFPHP to work with it. Short of
them (AMFPHP) releasing a major update of their owm, it would appear that
scouring the gargantuan library line-by-line to bring the Classes into php5
spec. UGH.