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: Benjamin Franksen <[email protected]>
To: [email protected]
Date: Wed, 3 Nov 2004 19:10:18 +0100
On Wednesday 03 November 2004 18:13, Steven Hunt wrote:
> This is something that people have wanted for a very long time - and
> rather than (as usual) talking - something has now been done about it. I
> think Cosylab have made a very good start (with of course a lot of input
> and help from Jeff). They should be congratulated for this. 

I am sorry if I may have given the impression that I see it in any different 
way. I do not. I wholeheartedly agree with the above.

> Of course it 
> is work in progress, 

Then why doesn't it say so? And why was all this not announced on tech-talk?

> but it has already proved useful in enabling a 
> wider audience to understand many aspects of the protocol rather than
> have to RTFSC.

Agreed.

> I seem to remember the epics rule that anyone with a bright idea should
> implement it.
>
> Sounds like you a volunteering to help or perhaps even fund this effort?
> that way you get it done how you like :)

Unfortunately I am in no position to provide funding. OTOH, I already started 
writing detailed technical comments on the individual sections of the 
document to point out weaknesses and provide feedback. I am quite familiar 
with CA myself which may help me to make the right guesses at what is 
probably meant by the more obscure explanations in the document. I am doing 
this in my spare time.

> We are lucky in the Epics community not to suffer from 'flame wars' on
> tech-talk - I hope we keep it that way.

I never wanted to start one. I offered criticism (which was never meant 
personally) and made a number of reasonable suggestions regarding the 
organisation of the collaboration on this. If that is interpreted as starting 
a flame-war, I will keep my mouth shut tight.

Ben

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

Navigate by Date:
Prev: Re: Channel Access Protocol Specification Hoff, Lawrence
Next: async driver john sinclair
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 Hoff, Lawrence
Next: RE: Channel Access Protocol Specification Dalesio, Leo
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 ·