Hi,

If the id attribute uniquely identifies the instance, why not using that to
check the (semantic) identity of the object instead of the reference?

Something like:

categories[1].id == user.category.id

Cheers
Juan Pablo Califano


2008/10/28, João Saleiro <[EMAIL PROTECTED]>:
>
> Hello,
>
> imagine the following scenario:
>
> - backend in AMFPHP;
> - a remote procedure that returns a complex type:
>
> Categories[]
>     CategoryVO (#12334)
>        id: 1
>        name: Accounting
>        etc...
>     CategoryVO (#34221)
>        id: 2
>        name: Reporting
>        etc...
>
>
>
> - Another remote procedure that returns another complex object:
>
>    UserVO (#5456)
>        id: 1
>        name: John Doe
>        CategoryVO (#2145)
>           id: 2
>           name: Reporting
>
> The category of the user John Doe is "Reporting", id 2. It's the same
> previously returned by the other service, on the position 1 of the
> categories array. The problem is that, on the client side:
>
> categories[1]==user.category
>
> is false. It's the same category, the problem is that when the object
> mapping occurs on the client side, it creates a new reference, so they are
> different instances of the same object.
> Right now, we need to make some loopings on the client-side to find and
> replace references. This involves a lot of work, and has performance
> considerations.
>
> Is it possible, or is there a solution to make same objects returned from
> the server side have same references on the client side?
>
> Thanks,
>
> João Saleiro
> *
> CTO @ Webfuel
> Adobe Community Expert
> Co-founder of the Portuguese RIA Community *
>
> [image: View João Saleiro's profile on 
> LinkedIn]<http://www.linkedin.com/in/jsaleiro>
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
>
>
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to