Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] PDom locking, lifecycle of PDom objects

Hi Doug,
please help me out on this, I really need to understand how to correctly
use locks on the PDom. I try to restate my question:

The implementation of the Call Hierarchy has the need to work 
with multiple PDoms, because such hierarchies may span over multiple
projects. I must not simultaneously hold locks of multiple PDoms
as this would lead to dead-locks. So I have to avoid locks where
possible and I have to understand under which circumstances this
is reasonable to do.

If there is no safe way to work with multiple PDoms we should
make changes to our architecture. That's why I'd like to understand
this as soon as possible.

Markus.

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schorn, Markus
> Sent: Montag, 04. September 2006 15:26
> To: CDT General developers list.
> Subject: [cdt-dev] PDom locking, lifecycle of PDom objects
> 
> Hi,
> I am trying to understand how to safely use the PDom. I have 
> a bunch of
> questions. I can only ask the first one, as the next one will 
> depend on
> the first answer. 
> 
> Objects obtained by the PDOM (e.g. PDOMName) will actually access the
> database when I invoke methods (e.g. PDOMName.toCharArray()) on them.
> What happens if the database was modified after the PDOM object was
> handed to me?
> 
> Markus.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 


Back to the top