Subject: |
Preemptive CA client that never calls ca_flush_io, ca_pend_io, ca_pend_event, nor ca_poll |
From: |
"J. Lewis Muir" <[email protected]> |
To: |
EPICS Tech-Talk <[email protected]> |
Date: |
Fri, 07 Nov 2014 16:35:45 -0600 |
Dear Tech-Talkers,
Is it quite acceptable to *never* call ca_flush_io, ca_pend_io,
ca_pend_event, nor ca_poll from a CA client using a preemptive mode CA
context?
I'm asking to try to untangle what is required and necessary for
preemptive vs. nonpreemptive mode. It seems to me that a channel can be
created with a connection state change callback, and ca_get_callback can
be used instead of ca_get (and similarly for other functions). In this
way, a preemptive-mode CA client could work correctly and never call
ca_flush_io, ca_pend_io, ca_pend_event, nor ca_poll. True?
Thanks!
Lewis
- Replies:
- Re: Preemptive CA client that never calls ca_flush_io, ca_pend_io, ca_pend_event, nor ca_poll Andrew Johnson
- Navigate by Date:
- Prev:
CA reference manual mystery function: ca_sg_pend J. Lewis Muir
- Next:
Re: Preemptive CA client that never calls ca_flush_io, ca_pend_io, ca_pend_event, nor ca_poll Andrew Johnson
- 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 reference manual mystery function: ca_sg_pend Johnson, Andrew N.
- Next:
Re: Preemptive CA client that never calls ca_flush_io, ca_pend_io, ca_pend_event, nor ca_poll Andrew Johnson
- 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
|