My understanding is that we are stuck at this place:
One position:
We support all data types native to the machine on which the client is
run. The ADO handles all conversions, gives native type for each channel
connected, gives sizeof infromation for allocating storage, and returns the
value in that type of variable - where the space is provided by the user.
The other position:
We support a limited number of types that support all of the data that
we need to support. The server puts the data into one of these limited set.
Otherwise, it is the same as above.
The difference in the two, is that the ADO handles many different types in
the first position and in the second position the server has to put data
into one of the limited set and the ADO only handles the limited set.
Is this right?
In the first place - the ADO is big and handles a lot. In the second place,
it is small and does not support everything.
Our clients will be about 70% JAVA, and 30% C. How much work is required to
get the functionality in the first option into all of these platforms? How
much is it in the second options?
Where is the example codes that implement the various client functions with
the proposed libraries?
Where is the protocol that was going to be placed on the wiki?
Thanks,
Bob
- Replies:
- Re: Channel Access Client Interface Kay-Uwe Kasemir
- RE: Channel Access Client Interface Jeff Hill
- Navigate by Date:
- Prev:
core meeting / presentation during EPICS meeting Matthias Clausen
- Next:
Re: Channel Access Client Interface Kay-Uwe Kasemir
- Index:
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:
core meeting / presentation during EPICS meeting Matthias Clausen
- Next:
Re: Channel Access Client Interface Kay-Uwe Kasemir
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|