[news.eclipse.tools.emf] Re: Attaching cdo adapters takes long time

[florian.pirchner@xxxxxxxxx (Florian Pirchner)]

Hi,

a short explanation. Further discussions will be added to the bugzilla.

Yes, a big chunk would be great.

View days ago i tried the different policies, but they did not match my 
requirements.

- org.eclipse.emf.cdo.view.CDORevisionPrefetchingPolicy
Defines how many CDOIDs should be resolved. This policy operates at one 
tree level.
- org.eclipse.emf.cdo.session.CDOCollectionLoadingPolicy
Defines how to load the elements in a collection. But does not allow to 
specify when the referenced elements of the collections elements are 
resolved. So it also operates at one tree level.

To get a good performance for redview, we need some kind of definition 
which allows to define the resolving depth. This means the depth of the 
tree which will be resolved and transfered to the client at load time.

For example a depth of -1 would allow to transfer the whole model (all 
containment references) at once to the client. So no additionally round 
trips for resolving the CDOID would be required.

Further this would allow a good performance for rendering the swt-ui.

I think your idea according the additionally option is really good. This 
might force the server to resolve all the objects in the model at load 
time.

Greetings, Flo