Hi Denise,

I have proven to be less than clear in my attempted explanations in the past, but here's my shot at it (with invitations to anyone to chime in with clearer explanation):

In the old days we would call that setting "internal switch(es)" to keep track of those things we are interested in, and make decisions in the program accordingly. Some of those decisions might mean re-setting the "switch".

In other words, it's a control mechanism that you make up for your own needs, the "switch(es) I allude to being the "semaphore(s)".

I hope this is helpful (or that someone finding it not to be so jumps in with clearer explanation).

Jim N

>Hi Jim,
>
>Probably an ignorant question here but what's semaphore implementation?
>Thanks.
>
>Denise
>
>>Hi Jim,
>>
>>Here I would agree wholeheartedly! But it *does* entail more than just setting Optimistic buffering to be active, and I think that is an important point for readers.
>>
>>Since the docs are not that clear (from what I can find, anyways) on "own" locking with buffering enabled, I suppose that some semaphore implementation would be safest.