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 | 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: write to a single element of an array field |
From: | "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov> |
To: | Ben Franksen <benjamin.franksen at helmholtz-berlin.de> |
Cc: | EPICS core-talk <core-talk at aps.anl.gov> |
Date: | Tue, 24 Mar 2020 17:14:35 +0000 |
Hi Ben, On Mar 24, 2020, at 12:02 PM, Ben Franksen via Core-talk <core-talk at aps.anl.gov> wrote:
Channel Access has always been allowed to throw away monitor updates if the client can’t keep up with the rate that the server is sending them, so a counter implemented like that isn’t reliable anyway. Ralph's change might make dropping updates more common,
but IIUC it only happens when your client is monitoring an array field through a filter. Maybe that’s more likely if you use a filter to only return the first element in order to reduce bandwidth needed say, but you still can’t guarantee to get all the events,
even with a scalar.
--
Complexity comes for free, simplicity you have to work for.
|