[Arp] value Object for amfphp
aral at ariaware.com
Tue Apr 19 03:04:37 PDT 2005
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.
* 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,
Folkert (Nederflash) wrote:
> In the journey to rebuild the birthday application, i have a 'maybe
> silly' question.
> For the openAmf and java remoting you use the Value Object, also in
> the birthday app.
> I see no need for this in amfphp remoting, but maybe i'm not right.
> So the question, should i use the value object for amfphp use or
> should i not (and hopefully why ?)
> For now the test setup hangs on getting the personList (gives back the
> rows but all undefined values )
More information about the Arp