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  <20182019  2020  2021  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021 
<== Date ==> <== Thread ==>

Subject: C++ APIs
From: Siniša Veseli <sveseli@aps.anl.gov>
To: <core-talk@aps.anl.gov>
Date: Wed, 18 Jul 2018 15:20:05 -0500
Hi,

I realize I have not been attending the working group meetings lately, so I apologize in advance if I missed something.

Reading through some of the github issues that seem to be getting a lot of attention recently, it seems like we are getting a completely new set of PVA client/server C++ APIs, which raises several questions in my mind:

1) Are those APIs becoming the "official" EPICS PVA client/server APIs? In other words, if I am starting a new C++ project based on EPICS7, should I start with the new interfaces, or work with the ones available in the most recent 7.0.1.1 release?

2) If #1 is true, what becomes of the current pvaClientCPP and pvDatabaseCPP APIs? Will those be deprecated? Or are we going to have two separate sets of high-level C++ APIs?

3) It looks like there are some rather significant differences in behavior between the new and existing interfaces. Have those differences been summarized anywhere?

I would imagine that making API changes like this, and for a project that numerous sites depend on, requires some sort of process: somebody comes up with a proposal and plan, there is a discussion about advantages/disadvantages and about the consequences for the existing code and for the future development, and (most importantly) there is an agreement between the developers as far as the direction that project will be taking. If this was discussed in one of the v4 meetings already, sorry that I missed it, and I would appreciate if someone points me to the document where all of this has been written down.

On a personal note, few years back, after we all decided that the new client API (pvaClientCPP) will be implemented, I had to put in a fair amount of work to replace my own high-level API with the official one, and I would not be exactly looking forward to yet another iteration of the same. However, if this was already discussed and agreed upon, then so be it.

Thanks for any clarifications,

Sinisa


--
Siniša Veseli
Scientific Software Engineering & Data Management
Advanced Photon Source
Argonne National Laboratory
sveseli@anl.gov
(630)252-9182


Replies:
Re: C++ APIs Michael Davidsaver

Navigate by Date:
Prev: Jenkins build is back to normal : epics-7.0-windows » STATIC,win32 #51 APS Jenkins
Next: Re: C++ APIs Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021 
Navigate by Thread:
Prev: Jenkins build is back to normal : epics-7.0 » linux32 #59 APS Jenkins
Next: Re: C++ APIs Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021 
ANJ, 06 Aug 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·