I don’t think that would be trivial even for just the Trap Write calls, the dbChannel layer doesn’t have access to the asClientPVT context pointer. For the other interfaces dbChannel doesn’t know anything about the client that is requesting access. I suspect the current arrangement may be the simplest, but I haven’t looked at it too closely.
- Andrew
> On Sep 2, 2019, at 9:08 AM, Zimoch Dirk (PSI) via Core-talk <[email protected]> wrote:
>
> On Mon, 2019-09-02 at 07:00 +0000, Zimoch Dirk (PSI) via Core-talk wrote:
>> Shouldn't PVA be implemented one level lower in dbChannel instead of in each network protocol?
>
> Sorry typo, I meant: Shouldn't access security be implemented in dbChannel?
> Dirk
- Replies:
- Re: pvPutLog? Michael Davidsaver via Core-talk
- References:
- pvPutLog? Timo Korhonen via Core-talk
- Re: pvPutLog? Zimoch Dirk (PSI) via Core-talk
- Re: pvPutLog? Michael Davidsaver via Core-talk
- Re: pvPutLog? Zimoch Dirk (PSI) via Core-talk
- Re: pvPutLog? Michael Davidsaver via Core-talk
- Re: pvPutLog? Timo Korhonen via Core-talk
- Re: pvPutLog? Michael Davidsaver via Core-talk
- Re: pvPutLog? Zimoch Dirk (PSI) via Core-talk
- Re: pvPutLog? Zimoch Dirk (PSI) via Core-talk
- Navigate by Date:
- Prev:
[Bug 1842086] Re: TestHarness should be TESTPROD instead of PROD Dirk Zimoch via Core-talk
- Next:
Jenkins build is back to stable : epics-base-3.15-test #124 APS Jenkins via Core-talk
- Index:
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:
Re: pvPutLog? Zimoch Dirk (PSI) via Core-talk
- Next:
Re: pvPutLog? Michael Davidsaver via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|