| [CDO] Long EList:s and caching [message #503194] |
Fri, 11 December 2009 00:48  |
Eclipse User |
|
|
|
Hello,
Assume I have a potentially VERY large list (EList) of a custom
EDataType (double[]). Also, there are two clients (clientA, clientB)
connected to the same CDO repository and they display the same list in a
table. If clientA adds a new element to the list and committs to the
server, how much is tranferred to clientB (over the wire) ?
Is it only the added element or the whole list or something inbetween?
Is it configurable?
Regards,
---
Anders
|
|
|
| Re: [CDO] Long EList:s and caching [message #503360 is a reply to message #503194] |
Sat, 12 December 2009 03:30  |
| Eclipse User |
|
|
|
Hi Anders,
Additions to lists, attributes or references, are locally captured as
deltas (or operations) and are committed to the repository as such. For
loading CDO does never use deltas at the moment. Reference lists can be
lazily and partially loaded. AFAIK this does not apply for attribute
lists. Maybe Simon can elaborate?
Cheers
/Eike
----
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Anders Forsell schrieb:
> Hello,
>
> Assume I have a potentially VERY large list (EList) of a custom
> EDataType (double[]). Also, there are two clients (clientA, clientB)
> connected to the same CDO repository and they display the same list in
> a table. If clientA adds a new element to the list and committs to the
> server, how much is tranferred to clientB (over the wire) ?
>
> Is it only the added element or the whole list or something inbetween?
> Is it configurable?
>
> Regards,
>
> ---
> Anders
|
|
|
Powered by
FUDForum. Page generated in 0.08722 seconds
Home