| 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: P4P release 3.4.1, now with gateway |
| From: | Michael Davidsaver via Tech-talk <[email protected]> |
| To: | EPICS Tech-Talk <[email protected]> |
| Cc: | "Slepicka, Hugo Henrique" <[email protected]> |
| Date: | Tue, 10 Dec 2019 08:24:55 -0800 |
On 12/10/19 8:22 AM, Michael Davidsaver wrote: > P4P 3.4.1 is available on github.com[1] and pypi.org[2]. How could I forget... https://anaconda.org/conda-forge/p4p courtesy of Hugo Slepika > In addition to the usual fixes, > this release is the first to include a PVAccess gateway (aka. proxy). This is installed > as the "pvagw" executable by both epics module and setuptools builds. > Documentation[3] is available. > > The feature highlights are configurable access control (aka access security) including > the use of "roles" (aka. *NIX group names) in addition to user names. Also logging of > Put operations. A number of gateway status PVs are added, including accounting of network > bandwidth used by clients/servers/PVs. > > This PVA gateway is intended to replace the prototype gateway from the pva2pva module. > Both use a similar JSON based configuration file. Config files for the prototype should > work with this new gateway. > > > Thanks to SLAC for sponsoring this work, and to Bruce Hill specifically for his stress testing. > > > [1] https://github.com/mdavidsaver/p4p/releases/tag/3.4.1 > [2] https://pypi.org/project/p4p/ > [3] https://mdavidsaver.github.io/p4p/gw.html > [4] https://github.com/epics-base/pva2pva >