> Now Im wondering its doing "new UserInfoEntityData()" that means that
> if multiple clients connect to my server call this getValueObject then
> every one of those clients will get a different reference to a
> different value object.
Yes.
> So different clients can update different details on different value
> objects!
Yes. Also note that a client merely updating a value object changes
nothing on the server side or in the database.
> however i want (ofcourse!) all of them to be synchronized
> with the same data!!
>
> Am I missing something about value objects?
Yes.
> aren't they synchronized around clients?
No.
Either, don't use value objects if it is not necessary for performance,
or use user transactions in the clients where updating value objects.

Signature
Øyvind Matheson Wergeland Just Another Virtual Application
Senior System Developer
Manamind AS Creating the Corporate Information Feed [tm]
Marek Lange - 11 Aug 2003 08:43 GMT
>> Now Im wondering its doing "new UserInfoEntityData()" that means that
>> if multiple clients connect to my server call this getValueObject then
[quoted text clipped - 8 lines]
> Yes. Also note that a client merely updating a value object changes
> nothing on the server side or in the database.
That's the point. Value objects are used to pass data from server to
client and vice versa. Changing a value object does not mean to change
the database data.
-marek