|
| Re: [CDO][0.8.0] TypeManager [message #105011 is a reply to message #105008] |
Fri, 21 December 2007 08:06  |
Eclipse User |
|
|
|
Originally posted by: stepper.sympedia.de
Hi Simon,
This is likely to be changed (removed) in the context of an existing
Bugzilla. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=213420#c5
"Particularly the HorizontalMappingStrategy doesn't require (by definition) a
central object table which could be used for id -> type lookups. When I
implemented that I decided to let the repository framework (TypeManager) help
those stores with hasEfficientTypeLookup()==false. It turned out that it was
not a good idea. I'll move this burden back to the store. There I'll provide a
central lookup table (cache) that is asynchronously fed through a QueueWorker
thread. Each MappingStrategy is prepared anyway to handle cache misses by
looking up the id withing the mapped object tables. This can be slow for
horizontal mappings and it seems to happen regularly in the current scenario."
Regards,
Eike Stepper
----
http://wiki.eclipse.org/CDO
http://wiki.eclipse.org/Net4j
Simon McDuff schrieb:
> Hi Eike,
>
> If we did disableLegacyObjects... Do we still need TypeManager ?
>
> Everywhere the code we do the following :
>
> repository.getTypeManager().registerObjectType(..).
>
> But in fact I never use it.
>
> Should We desactivate it in the case where disableLegacyObject is true ?
>
> Also, accumulating values like TypeManager... we will run out of memory.
>
> Thank you
>
>
>
|
|
|
| Re: [CDO][0.8.0] TypeManager [message #612948 is a reply to message #105008] |
Fri, 21 December 2007 08:06 |
|
Hi Simon,
This is likely to be changed (removed) in the context of an existing
Bugzilla. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=213420#c5
"Particularly the HorizontalMappingStrategy doesn't require (by definition) a
central object table which could be used for id -> type lookups. When I
implemented that I decided to let the repository framework (TypeManager) help
those stores with hasEfficientTypeLookup()==false. It turned out that it was
not a good idea. I'll move this burden back to the store. There I'll provide a
central lookup table (cache) that is asynchronously fed through a QueueWorker
thread. Each MappingStrategy is prepared anyway to handle cache misses by
looking up the id withing the mapped object tables. This can be slow for
horizontal mappings and it seems to happen regularly in the current scenario."
Regards,
Eike Stepper
----
http://wiki.eclipse.org/CDO
http://wiki.eclipse.org/Net4j
Simon McDuff schrieb:
> Hi Eike,
>
> If we did disableLegacyObjects... Do we still need TypeManager ?
>
> Everywhere the code we do the following :
>
> repository.getTypeManager().registerObjectType(..).
>
> But in fact I never use it.
>
> Should We desactivate it in the case where disableLegacyObject is true ?
>
> Also, accumulating values like TypeManager... we will run out of memory.
>
> Thank you
>
>
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.01488 seconds
Search
Help
Register
Login
Home
