[Arp] value Object for amfphp

[matthi]

Aral Balkan wrote:

> Hi Folkert,
>
> Value Objects (or Transfer Objects) are an essential part of the 
> framework. They encompass all the data needed to perform a business 
> function (eg. send an email, update or set a person's information, 
> etc.) in a single object.
>
> Advantages:
>
> * All related data is encapsulated in a single object
> * One object is passed around, both client-side and server-side (no 
> more, "how many arguments were we expecting... what were their 
> types?"-type questions between the client and server teams.)
> * Anyone can check the contract easily by looking at the VO class
> * Inconsistencies between client/server expectations can be 
> immediately seen and acted upon.
>
> All the best,
> Aral
>
That sounds all right, but I came up using the singleton approach for 
this kind of stuff.

That´s what I thought would be better.

That way I just call the getInstance() function of a given Object rather 
then call´s some function in the viewRef giving me back the valueObjects 
properties

This looked for me much smarter....

As I am a designer and not a programmer I would like to hear the pros 
and cons about this approach

For me it works like a charme and imho it´s much more comfortable

Regards

Matthias Oesterle