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: Channelfinder Recsync Client: Limit records client side |
From: | "Kenner, Daniel Craig via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Tynan Ford <TFord at lbl.gov> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Thu, 9 May 2024 22:46:44 +0000 |
Hey Tynan, thanks for getting back to me. Indeed, after I sent my email yesterday, I tore into the Recsync Client module and discovered much the same. Unfortunately, we can’t limit it at the cfstore level as the client oversees setting up the recsync
server and I can’t hand them a precompiled version. Given these restrictions I have created my own version that injects a field parser in the function where the recsync client pushes to the server. It scans the info fields and only allows the record to be sent
if it has a specific info(key, value) pair. Additionally, I edited the caster struct to include a field you set in the st.cmd file to enable this behavior. My current solution is a little bit janky, but I think with some polish it could be a real a useful addition. Do you happen to know who I should contact if to discuss getting this included in the Recsync Module
on Git? Unclear on who owns the repo. From: Tynan Ford <TFord at lbl.gov>
Hi Daniel, I am not aware of any field like that but it does sound like an interesting idea. Another place you could filter PVs before they reach channel finder is on the recceiver side, in the cfstore plugin. Best, Tynan On Wed, May 8, 2024 at 6:32 PM Kenner, Daniel Craig via Tech-talk <tech-talk at aps.anl.gov> wrote:
|