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  <20152016  2017  2018  2019  2020  2021  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  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: epics:// vs. ca:// Re: epics docker container
From: Carlos Pascual <[email protected]>
To: <[email protected]>
Date: Wed, 16 Dec 2015 19:42:32 +0100
Hi! 

Thanks a lot for the suggestions and the comments.

I was unaware that there were already applications using URIs for 
channel access (I did only a shallow search before implementing the 
taurus-epics plugin). Are there any documents detailing the 
specifications for "ca" URIs?
Specifically it would be great to learn about standard conventions for 
the "authority", "path", "query" and "fragment" parts of the URI (just 
to avoid doing it in inconsistent ways like I did for the "scheme" part)

I'll definitely change  the scheme to "ca" (and "pva" if I go into epics 
v4). At this moment, the epics plugin in taurus is just a proof-of-
concept so there is no problem in doing such changes. In fact, my 
intention is to port what we had in Taurus v3 to taurus v4 and then 
leave it for someone interested in developing it further (we do not use 
epics at ALBA).

Also, thanks for the pointers to the docs.

Cheers




On Wed 16 December 2015 14:54:24 Kasemir, Kay wrote:
> On Dec 16, 2015, at 4:41 AM, Ralph Lange <[email protected]> wrote:
> > One more remark  about
> > 
> > > $ taurusform epics://XXX:random epics://XXX:a epics://XXX:b
> > > epics://XXX:sum> 
> > The EPICS V3 network protocol is called Channel Access. In URI-type
> > notation, applications should use "ca:" to denote the scheme. The
> > EPICS V4 (next generation) network protocol is called PV Access.
> > Its common URI scheme tag is "pva:". Unless the "epics:" tag stands
> > for something taurus-internal that is a different scheme and not
> > Channel Access, I would really prefer a consistent naming.
> Couldn’t agree more.
> 
> CS-Studio contributed to this confusion because it allows “epics://“
> as well as “ca://“. Using "epics://“ seemed logical to some of the
> involved parties at the time because end users talk to “EPICS”, but
> using the underlying protocol “ca://“ (or by now also “pva://“) is
> better in the long run, plus fewer characters to type.
> 
> Thanks,
> Kay

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: [email protected]
 Phone: +34 93 592 4428
+----------------------------------------------------+



References:
epics docker container Carlos Pascual
Re: epics docker container Ralph Lange
epics:// vs. ca:// Re: epics docker container Kasemir, Kay

Navigate by Date:
Prev: RE: areaDetector plugin: very large output array Mark Rivers
Next: Re: epics docker container Carlos Pascual
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: epics:// vs. ca:// Re: epics docker container Kasemir, Kay
Next: Re: epics docker container Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·