Can duplicated objects remain duplicated when transfered to javascript?

[Paul Extance]

I have a case where I'm transferring a large graph of data from Java to JavaScript as a result of a method invocation via DWR (using v.2.0)
Many of my POJOs contain a reference to a User  POJO.  This User POJO is refereced 100's of times in the graph of objects, and in Java there really is only one copy of this object.

When this moves across to javascript I'm hoping the User POJO is not converted 100's of times and that in JavaScript we have 100's of copies of this object.

Looking at how the javascript is written where objects are re-assembled object by object, it would look like this optimization is possible.

So Can DWR do this, and if so do i need to tell it to, or is this default behavior?

Thanks

PaulE

[Lance Java]

This is the default behaviour

Cheers,
Lance.

2008/6/24 Paul Extance <paul.extance@...>:

I have a case where I'm transferring a large graph of data from Java to JavaScript as a result of a method invocation via DWR (using v.2.0)
Many of my POJOs contain a reference to a User  POJO.  This User POJO is refereced 100's of times in the graph of objects, and in Java there really is only one copy of this object.

When this moves across to javascript I'm hoping the User POJO is not converted 100's of times and that in JavaScript we have 100's of copies of this object.

Looking at how the javascript is written where objects are re-assembled object by object, it would look like this optimization is possible.

So Can DWR do this, and if so do i need to tell it to, or is this default behavior?

Thanks

PaulE