EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: announcing PVXS (now with client)
From: Michael Davidsaver via Core-talk <core-talk at aps.anl.gov>
To: EPICS core-talk <core-talk at aps.anl.gov>
Date: Thu, 5 Mar 2020 18:40:34 -0800
As an update on this project.  The client part of the library is now working.
So I'd like to ask for feedback from adventurous individuals.

In particular, while the present API exposes (almost) all of the PVA protocol,
I don't consider this API frozen or final in a version 1.0 sense.
I'd like to invite those who have complained about the existing pvAccessCPP
to take a look.  There is still time for changes.

The documentation linked below has been updated, and a set of (fairly primitive)
CLI tools is included.  This might be a good place to start looking.

https://github.com/mdavidsaver/pvxs/tree/master/tools


On 2/7/20 8:30 AM, Michael Davidsaver wrote:
> Now that it's far enough along to be interesting I'd like to announce more
> widely a project I've been working on for the past few months (with support
> from ORNL).
> 
> The PVXS library is another PVAccess protocol server and client.
> This will be a reimplementation of the pvDataCPP and pvAccessCPP modules.
> 
> I'm making this announcement now in the hope of soliciting feedback.  I am interested
> in hearing impressions from those who have used pvDataCPP and pvAccessCPP in anger.
> One of my motivations is to create an API which is easier to understand,
> and less error prone.
> 
> At present, the server component is working, and I think near being feature complete.
> It's tested against clients using the pvAccessCPP module (eg. pvget and friends),
> and both of the Java implementations.  Of course at this stage bugs should be expected.
> I haven't started on the client component yet.
> 
> The code can be found at https://github.com/mdavidsaver/pvxs
> 
> Such documentation as I've written can be found here
> https://mdavidsaver.github.io/pvxs/
> 
> Note that this code requires a toolchain supporting c++11 or later.
> This is gcc >=4.9.  It also depends on the libevent library >=2.0 .
> 
> While I think the basic form of the server side API is settling down,
> it is not finalized and will change to some degree prior to an initial release.
> 
> I think a reasonable entry point investigation is the mailbox server demo.
> 
> https://github.com/mdavidsaver/pvxs/blob/master/test/mailbox.cpp
> 
> I don't have any concise demos of data handling (Value container class).
> The code behind the mailbox Put handling is one simple case.
> 
> Beyond this, please ask questions.
> 


References:
announcing PVXS Michael Davidsaver via Core-talk

Navigate by Date:
Prev: Build failed: EPICS Base base-7.0-554 AppVeyor via Core-talk
Next: Build failed: epics-base base-epicsTempFile-C-12 AppVeyor via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: announcing PVXS Michael Davidsaver via Core-talk
Next: [Bug 541353] Re: epicsThreadSleepQuantum() not accurate mdavidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
ANJ, 05 Mar 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·