EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20202021  2022  2023  2024  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Announcing PVXS
From: Jeong Han Lee via Tech-talk <tech-talk at aps.anl.gov>
To: Michael Davidsaver <mdavidsaver at gmail.com>
Cc: EPICS Tech-Talk <tech-talk at aps.anl.gov>
Date: Tue, 14 Apr 2020 10:36:45 -0700
Hi Michael,

   Thank you for this great work.  And thank ORNL and Kay also.

   Best,
   Han

On Mon, Apr 13, 2020 at 7:47 PM Michael Davidsaver via Tech-talk
<tech-talk at aps.anl.gov> wrote:
>
> I'd like to announce the existence of the PVXS module to those who
> don't lurk on core-talk.  This is a new C++ implementation of a
> PVAccess protocol client and server.
>
> Documentation is available:
>
> https://mdavidsaver.github.io/pvxs/
>
> An example server and client
>
> https://mdavidsaver.github.io/pvxs/example.html
>
> I'd like to thank ORNL, and Kay Kasemir specifically, for supporting
> this work.
>
>
> To be clear, and to answer the obvious question first, PVXS is
> a functionally equivalent rewrite of the pvDataCPP and
> pvAccessCPP modules.  It is not a wrapper.
>
> My aim is to build upon a decade of experience with pvDataCPP/
> pvAccessCPP, and a decade of improvements to the C++ language,
> to provide a more stable and usable library.
>
> This code has been developed over the past 6 months, and is
> I think feature complete for an initial release.  However, it has
> not seen much testing by people other than myself. So I have
> difficulty in presenting this as a final, set in stone, API.
>
> Therefore, this announcement is the start of what I'm calling this
> a "public beta" period.  During this time, which I hope will
> be less than 6 months, breaking API changes are acceptable.
>
> Does this mean that there will be breaking API changes?
>
> Maybe.  I anticipate refinements more than major changes,
> but I won't rule anything out.
>
> I'm happy to work with anyone who tries to use PVXS during this
> period to help mitigate any pain which might arise from future
> changes.  (If I know what you're doing I'll try not to break it)

References:
Announcing PVXS Michael Davidsaver via Tech-talk

Navigate by Date:
Prev: RE: StreamDevice, prevent records from getting "stuck" Sobhani, Bayan via Tech-talk
Next: epicsqt: getting started questions John Dobbins 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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Announcing PVXS Michael Davidsaver via Tech-talk
Next: epicsqt: getting started questions John Dobbins 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  <20202021  2022  2023  2024 
ANJ, 14 Apr 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·