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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Receiving duplicate monitor values using CA PV Gateway |
From: | Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
Date: | Thu, 27 Aug 2020 18:47:10 +0200 |
On Aug 27, 2020, at 9:45 AM, Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> wrote:
Now, in that -no_cache mode, when a monitor connection to the PV exists and an additional external client connects - what should the Gateway do?It doesn't have the cached value, so it must do another get() on the inside to the IOC. When the answer to that get() arrives, it can't be distinguished from a monitor update. So with a list of clients for that PV, which ones should get the update, which shouldn’t?
Why can’t that ca_get_callback() be distinguished, couldn’t it use a different pFunc and/or pArg than the monitors use? That would allow the gets to trigger different behavior (i.e. not update the cached value or forward this event to the monitoring clients).