Re: [amfphp] amfphp advantages?

[<ham...@t-...>]

Hi,

in simple terms (and the same holds for xml): if your data structure is simple,
it does not help much. Say you request a list of products from a job search,
and they are all
ordernr, descr, price, image_url
The code to pick up data from loadvars is simple

Read it the other way round: once your data structure becomes complex (some entries may
have extra fields, and these again are structured), traditional code would require to define
a specific way to send the data across and unpack them
(suppose the shop does not have an image for every product, but if it has, it comes with
url, width, and height.
Even consider a menu with submenus and sub-sub-menus)

Wolfgang

>> 
>> hi, please dont hurt me :)=20
>> 
>> i recently broke my head against getting multiple database calls to =
>> work. i changed to the latest build, changed my paths to absolute, and =
>> nothing worked. ( i didnt get around to trying amfphp lite) - i was in a =
>> big hurry so i just used the loadvars object. it worked easily and it is =
>> almost as fast as amfphp.=20
>> 
>> this made me wonder - why do i love amfphp again? what are the =
>> advantages of using amfphp over simple old loadvars? someone was asking =
>> me this at lunch a week ago and i had to bluff about the flexibility, =
>> speed, ability to return the results object, etc...=20
>> 
>> but i want to hear it from you guys - you who should know better than =
>> all else - why is AMFPHP critical. why should i not start using loadvars =
>> in all my projects instead?=20
>> 
>> not trying to be argumentative, i still love AMFPHP,
>> 
>> Jonathan
>> 
>> 
>> 
>>