Peregrine McGehee wrote:
>
> At the last collaboration meeting (during ICALEPCS) there was a
> lengthly discussion during Jeff's talk on the "Portable CA Server
> status" that dealt with the relationship between CA, PCAS, and cdev.
>
> I recall a statement being made that the functionality of the CA
> client API may be reduced in future releases (4.0+?) under the
> assumption that most client applications will be using a cdev layer to
> reach CA.
We intend to maintain backwards compatibility with the existing
CA client API. Funding permitting, we will also produce a next
generation CA client API/CA protocol with an emphasis on improved
performance, efficiency, and ease of use.
> 2) if you need to transport complex data types, or perform any kind
> of transaction processing, and don't need EPICS applications, use cdev.
> This is available now, and it is not too hard even to implement a
> custom server starting from Walt's skeleton.
The PCAS API supports begin/end transaction and complex data types.
Full access to these capabilities from the CA client API will
of course require revisions to the CA protocol/CA client API.
Jeff
______________________________________________________________________
Jeffrey O. Hill Internet [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos, NM 87545 USA FAX 505 665 5107
- References:
- CA API: Future directions? Peregrine McGehee
- Navigate by Date:
- Prev:
S: CapFast Symbols for mbb*Direct Ralph Lange
- Next:
Re: S: CapFast Symbols for mbb*Direct Graham Waters
- 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: CA API: Future directions? Peregrine McGehee
- Next:
Softwaare Distribution Bakul Banerjee
- 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
|