EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: CA protocol documentation.
From: "Brian McAllister" <[email protected]>
To: "'EPICS \(E-mail\)'" <[email protected]>
Date: Thu, 14 Nov 2002 13:41:43 -0500
Jeff, Ralph, et. al:

Is it just me, or do you sound just a bit paranoid ?

You seem to suggest that the only use for a protocol spec would be to write
"alternate implementations of the core system libraries".

Suppose we want:

- to know exactly what is going across our networks.

- to be able to put a network analyzer on the wire and configure it to
  display EPICS traffic in some meaningful fashion.

- to know what the current capabilities and limitations of the protocol
  (rather than the API) really are.

- to understand how the protocol works so we can have meaningful opinions
  on how it might be further developed.


Just because I want to have the TCP/IP spec for reference doesn't mean I'm
interested in writing my own protocol stack.

The argument that fully documenting CA requires significant effort that may
not be available given current resources and priorities seems quite
reasonable.
The idea that it is somehow "dangerous" to provide the details (which can
of course be obtained by sufficient study of the code) does not.

----
Brian McAllister                    Controls Programmer/Beam Physicist
[email protected]                        MIT-Bates Linear Accelerator
(617) 253-9537                                           Middleton, MA

Replies:
RE: CA protocol documentation. Jeff Hill

Navigate by Date:
Prev: RE: CA protocol documentation. Jeff Hill
Next: caTCL headerfiles vijayram v g
Index: 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  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: CA protocol documentation. Chip Watson
Next: RE: CA protocol documentation. Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  <20022003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·