On 7/13/21 7:10 AM, Pogacnik, Matic via Tech-talk wrote:
> Hi all,
>
> We are working on the P4P gateway to add the ability to reload the ASG/PVLIST
> configurations. We were successful in applying the new configuration to the
> new connections (draft PR: https://github.com/mdavidsaver/p4p/pull/70),
> but we have problems applying new rules to the existing connections (monitors).
> Can someone familiar with the codebase provide any tips, please?
> I would
> especially like to know where the list of the existing connections is stored
> and all the metadata (hosts/username/aliases) used to open and validate
> these connections.
I didn't see this specific question on the PR. The channel list is being kept
down in the AS machinery in the 'Engine._anodes' dict.
https://github.com/mdavidsaver/p4p/blob/bf8d637d7edc9dde7c2acbacbbb6c73d8f194e6b/src/p4p/asLib/__init__.py#L49
This is how permissions changes resulting from CALC rules are handled.
https://github.com/mdavidsaver/p4p/blob/bf8d637d7edc9dde7c2acbacbbb6c73d8f194e6b/src/p4p/asLib/__init__.py#L201
Also, while I don't think there will be any substantial conflicts,
I would suggest seeing how your changes apply on top of:
https://github.com/mdavidsaver/p4p/pull/54
- References:
- P4P gateway development question Pogacnik, Matic via Tech-talk
- Navigate by Date:
- Prev:
Re: Building autosave with EPICS 7.0.6 and RTEMS5 Michael Davidsaver via Tech-talk
- Next:
Re: Event Recordings -- Epics Spring 2021 Phillip A. Sorensen via Tech-talk
- 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
- Navigate by Thread:
- Prev:
P4P gateway development question Pogacnik, Matic via Tech-talk
- Next:
Block CAPUT to not be able to modify PV value Adrian Martinez via Tech-talk
- 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
|