> No, SVNClientSynchronized contains a static member variable
> that it synchronizes all access to SVNClient around. It just
> so happens that they use a Class object for the member
> variable. That is what I meant.
I understand now (after I looked at the code :)), thanks!
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: Mark Phippard [mailto:markp@softlanding.com]
> Sent: Monday, November 14, 2005 22:11
> To: alex@tmate.org
> Cc: dev@subversion.tigris.org
> Subject: RE: r17214, JavaHL thread local storeage and reentrant calls
>
> "Alexander Kitaev" <alex@tmate.org> wrote on 11/14/2005 04:04:43 PM:
>
> > If you're talking about non-static synchronized java methods, then
> > non-static methods uses object monitor for synchronization,
> not class
> one:
>
> No, SVNClientSynchronized contains a static member variable
> that it synchronizes all access to SVNClient around. It just
> so happens that they use a Class object for the member
> variable. That is what I meant.
>
> I believe the technique that is being used in
> SVNClientSynchronized is fully thread-safe and is fairly common.
>
> Mark
>
>
>
> ______________________________________________________________
> _______________
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe
> Plc by IBM Email Security Management Services powered by MessageLabs.
> ______________________________________________________________
> _______________
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 14 22:26:21 2005