EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  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  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Channel Access Protocol Specification
From: "Hoff, Lawrence" <[email protected]>
To: EPICS Techtalk <[email protected]>
Date: Wed, 03 Nov 2004 12:42:12 -0500

I, for one, agree with the sentiment that criticism *must* be constructive, and inherently comes with a promise of help.

	I also think that initiating the process of specifying CA
at the network protocol level in a public way has tremendous benefit,
not only in allowing alternate implementations, but also in providing
a framework for discussion of *existing* implementations. All involved
in the process so far should be commended.

	I do share Ben's concerns that this document is in its
infancy, and has the potential to mislead readers into thinking that
it is more complete than it is at present. It is also not clear to
me how open the process is for improving the document.

	I read through it and ended up with quite a few unanswered
questions (e.g. what should the CA server behavior be if a duplicate
CA_PROTO_EVENT_ADD message is received with an identical Subscription
ID).

	It seems to me that any of us who are capable of, and interested
in assisting in this effort must organize ourselves in a way that
allows such questions to be raised, understanding to be achieved,
and clarifications to be made to the document. In some cases,
such clarifications might even result in necessary changes to
*existing* implementations (e.g. to address situations not previously
anticipated, such as out-of-order packets).

	Is COSYLab interested in setting up a Wiki or other
collaborative environment so folks can pitch in and help out?

-- Larry


References:
Channel Access Protocol Specification Benjamin Franksen
Re: Channel Access Protocol Specification Steven Hunt

Navigate by Date:
Prev: Re: Channel Access Protocol Specification Steven Hunt
Next: Re: Channel Access Protocol Specification Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Channel Access Protocol Specification Steven Hunt
Next: Re: Channel Access Protocol Specification Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  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 ·