Experimental Physics and
Industrial Control System

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

Replies:

Re: epics:// vs. ca:// Re: epics docker container Carlos Pascual

References:

epics docker container Carlos Pascual

Re: epics docker container Ralph Lange

Navigate by Date:

Prev: Re: epics docker container Michael Davidsaver

Next: areaDetector plugin: very large output array Phil Atkin

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 

Navigate by Thread:

Prev: Re: epics docker container Ralph Lange

Next: Re: epics:// vs. ca:// 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  <2015>  2016  2017  2018  2019  2020  2021  2022  2023  2024