EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Channel Access monitoring tools
From: Benjamin Franksen <[email protected]>
To: <[email protected]>
Date: Tue, 15 May 2012 12:59:00 +0200
On Tuesday, May 15, 2012, you wrote:
> > > At present, I am doing something like this:
> > > 
> > > 1.  Invoke ca_create_channel() with a connection state change
> > > handler.
> > > 
> > >     The connection state change handler sets a flag to indicate that
> > >     the connection has complete.
> > > 
> > > 2.  Call ca_pend_io() to make sure the request is sent on its way.
> > 
> > You want to use ca_flush (or was it called ca_flush_io?) for that.
> > AFAIK ca_pend_io does not send accumulated requests, it just waits for
> > responses (and other events).
> > 
> > Cheers
> > Ben
> 
> I'm not sure about that.  The first sentence of the description for
> ca_pend_io() says:
> 
>   Flushes the send buffer and then waits until outstanding queries
> complete or the specified time out expires.
> 
> When I look at the source code for EPICS Base 3.14.12.2, I see that
> ca_pend_io() gets a ca_client_context object in the variable "pcac" and
> then calls the pcac->pendIO() method of that object.  The pendIO()
> method, in turn calls the this->flush() method of the same object.
> ca_flush_io() instead directly calls pcac->flush() on the context
> object.  So it looks like ca_pend_io() does everything that
> ca_flush_io() does and more.

Sorry for the misinformation, then.

Cheers
Ben

Attachment: signature.asc
Description: This is a digitally signed message part.


References:
Channel Access monitoring tools Bill Lavender
Re: Channel Access monitoring tools Benjamin Franksen
Re: Channel Access monitoring tools Bill Lavender

Navigate by Date:
Prev: FW: Problem installing CA for QT Andrew Rhyder
Next: Re: Channel Access monitoring tools Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Channel Access monitoring tools Bill Lavender
Next: RE: Channel Access monitoring tools Hill, Jeff
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·