To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=93051





------- Additional comments from [EMAIL PROTECTED] Fri Aug 29 08:52:23 +0000 
2008 -------
Hi Kay - thanks for the input:

> Classically, no Uno object is allowed to keep a lock while calling out ...
> means, that we have two bugs here,

    Seems reasonable. On the other hand, presumably there are some parts of the
system so basic & fundamental that presumably we don't want to have this
requirement. One might assume calling out to this would be one of these ?

> If only one kept a lock, there obviously wouldn't a problem ;-)

    Sure.

> Quick fix is to just "disarm" it by removing the "unsafe" declaration.

    Sounds good, where is that decl ?

> Plan basically is (as stated somewhere in the wiki), to move all but some 
> office objects into an "unsafe" environment. The ones not to be moved
> just ensuring some basic parallelism e.g. for I/O or configuration access.

    Sure, I'm just concerned that we keep the core safe.

> -> Michael, do you see a chance to release the config manager lock
> while calling out?

    Well that bit is at least possible - just add "UnoApiLockReleaser
aReleaser;" type instances around the place. The more tricky piece is verifying
that that is 100% correct in all cases, and of course - we don't want to be
releasing the lock each time we write bytes to a stream eg. ;-) - do we really
have to drop it on -every- call out ? or can we be fairly happy that simple I/O
writes to a file will not be blocking on configuration access ?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to