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>
Sent: Thursday, May 9, 2024 3:25 PM
To: Kenner, Daniel Craig <kenner2 at llnl.gov>
Cc: tech-talk at aps.anl.gov
Subject: Re: Channelfinder Recsync Client: Limit records client side
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.
Hello all,
I have been working with LLNL on an EPICs application. The Channelfinder has critical functionality we would like to take advantage of, but one of the hurdles is limiting what records
are allowed to be published through the reccaster module. I don’t want the end user to have visibility into every single record an IOC has, but I am unclear if the support module offers this functionality. Is there some field I can add to relevant records
so that reccaster only publishes those PV’s?
Thank you for your time,
Daniel Kenner
Computer Engineer
Lawrence Livermore National Laboratory
Phone: (925) 758-2607
Email:
kenner2 at llnl.gov