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: "Jeff Hill" <[email protected]>
To: "'Tim Mooney'" <[email protected]>
Cc: "EPICS-tech-talk" <[email protected]>
Date: Thu, 14 Nov 2002 15:06:44 -0700

> Although pure java would probably have debilitating limitations,
> it would also provide significant benefits for our users, 
> in niche applications.

I am certainly no expert on java, but it seems that a "pure java"
version of the ca client library would be somewhat at odds with the
normal domain of java which from my perspective is rapid prototyping,
code component integration, and web development. There may be advantages
in using a JNI to jump into optimized C or C++ code when something low
level needs to be done, and efficiency is important. An example of this
is the java implementation of a hash table. Admittedly, there are
complications with expanding the "sand box", but I assume that a java
expert can overcome these problems by maintaining architecture specific
downloads on a central website. Certainly the JNI approach is a good way
to reduce CA system code maintenance and upgrade duplication.

> But in the protocol area, the effort of someone incapable
> of collaborating would not produce anything of value
> anyway, so it would be fine and maybe even preferable for such
> a wheel to spin freely.

Unless we end up with unique and independent protocol interfaces
spinning freely, but incompatibly, within each and every project with no
hope for interoperability and leveraged effort.

Jeff


Replies:
RE: CA protocol documentation. Christopher A. Larrieu
Re: CA protocol documentation. Chip Watson
References:
Re: CA protocol documentation. Tim Mooney

Navigate by Date:
Prev: Re: CA protocol documentation. Tim Mooney
Next: RE: CA protocol documentation. Christopher A. Larrieu
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. Tim Mooney
Next: RE: CA protocol documentation. Christopher A. Larrieu
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 ·