Arnulf,
Arnulf Wiedemann wrote:
yes understood, that is what I did. And if it is not the first call and I have
used different objects in the meantime, I can send and empty oid with the
appropriate cache_index. Is that correct?
Yes, correct. One can just think as the server cache entries being
managed by the client.
It is certainly _OK_ to always provide all of the above info and to just
leave the caching out. If you want to utilize the cache, you need to
provide cache indexes for the different Ids and need to memorize the
usage of these indexes for reference/replacement on the client side.
ok, that is what I am doing.
My question was: how do I tell the server to forget about the object (means to
decrement the reference count for that object by 1). I thought that is done
with the release call?
That is also correct. The object destructs itself with the last release
call, independent from any cache entries (at least in theory). It is the
clients task, to ensure the servers cache entry consistence and correct
usage, e.g. as not referencing dead references.
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
