| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Lock/Mutex to prevent "caget" from cutting in between updating multiple fields |
| From: | Till Straumann <[email protected]> |
| To: | Michael Davidsaver <[email protected]>, [email protected] |
| Date: | Mon, 2 May 2016 08:24:13 -0700 |
That confirms how I had read the code and which was the basis for my answer. Thanks - T. On 05/02/2016 05:13 AM, Michael Davidsaver wrote:
On 05/01/2016 04:57 AM, Ralph Lange wrote:Correct. In the congestion case, i.e. when the array data in the record gets updated before an older event is posted, the CA server will send an update to the client that combines the old time stamp (taken from the queue) with the newer data (taken from the record).From looking at getOptions() (called via dbGet()) it looks like type==dbfl_type_rec ignores db_field_log::time and fetches from the record directly? So to my understanding value, alarm, and timestamp should *always* be consistent. http://bazaar.launchpad.net/~epics-core/epics-base/3.14/view/head:/src/db/dbAccess.c#L371