Let me just add one point to clarify the situation as it is.
> > 6. In general a set of records may be processed as a result of
> > a single dbPutNotify. If a record in the set is found to be active,
> > either because PACT is true or because a putNotify already owns the
> > record, then that record is not made part of the set of records
> > that must complete before the putNotify request completes.
I verified that indeed it does not matter *why* the asynchronous record
is active. My example behaves in exactly the same way if I start with a
plain caput (w/o callback), i.e. the second put (the one with callback)
completes immediately.
Cheers
Ben
- References:
- ca_put_callback once again Ben Franksen
- Re: ca_put_callback once again Andrew Johnson
- Re: ca_put_callback once again Ben Franksen
- Navigate by Date:
- Prev:
RE: Incorrect get_precision Allison, Stephanie
- Next:
sncseq compiling error 王锐萍
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: ca_put_callback once again Andrew Johnson
- Next:
RE: ca_put_callback once again Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|