Difference between revisions of "V4 CA Client User Interface"
From EPICSWIKI
KayKasemir (talk | contribs) (split off name server page) |
KayKasemir (talk | contribs) (Update with link to ZeroC ICE) |
||
| Line 1: | Line 1: | ||
== Channel Access Client User Interface == | == Channel Access Client User Interface == | ||
Under V4, a ProcessVariable would no longer be limited | |||
to the current properties 'value', 'units', ... but allow the users to create | |||
CA servers and clients that understand new properties. | |||
* | |||
The low-level V4 CA client API is likely to be rather complex because it | |||
now needs to handle arbitrary property catalogs. | |||
* There still needs to be an easy to use high-level API, not much more complex than the existing one. | |||
* There needs to be access to CA from languages like Matlab in a way that's as easy as | |||
pv = caopen('fred'); | |||
value = caget(pv); | |||
== Food for thought == | |||
Is there anything we can learn from other communication libraries? | |||
* A brief look at [[ZeroC ICE]] | |||
Revision as of 14:59, 15 June 2005
Channel Access Client User Interface
Under V4, a ProcessVariable would no longer be limited to the current properties 'value', 'units', ... but allow the users to create CA servers and clients that understand new properties.
The low-level V4 CA client API is likely to be rather complex because it now needs to handle arbitrary property catalogs.
- There still needs to be an easy to use high-level API, not much more complex than the existing one.
- There needs to be access to CA from languages like Matlab in a way that's as easy as
pv = caopen('fred');
value = caget(pv);
Food for thought
Is there anything we can learn from other communication libraries?
- A brief look at ZeroC ICE
