Stephan Bergmann wrote:
The overall validity of turning off MUSTREPLY and SYNCHRONOUS for a
normal (not one-way) UNO interface method invocation is at least
questionable. One basic property of UNO is that a sequence of method
invocations (of not--one-way methods) is executed sequentially, in a
single UNO thread.
This is guaranteed anyway, respectively might be controlled by the
caller. Again, forcing synchronous calls to asynchronous behavior would
have been offered via CuCas and is not yet utilized.
The reason for acquiring objects passed in synchronous calls is the
"acquire" method being oneway, avoiding potential races between a
client acquiring (sending an acquire request) an object passed to a
synchronous call and returning from this synchronous call.
There is neither an acquire method in UNO (com.sun.star.uno.XInterface's
acquire is an implementation detail of the C++--UNO language binding,
that unfortunately got exposed), nor is there an acquire message in URP.
Correct. For the above reasons, this is not needed (has been avoided).
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
