Experimental Physics and
Industrial Control System

Hi:

I think Ralph's recent answer with regard to the gateway already shows
that we can _not_ support all data types native to the machine
on which the client is run.

We have to agree on a limited set of types
because the gateway must understand all types
in order to compare the values against deadbands etc.

Next question:
- What is on that list of supported types?
Does it include unsigned types?
Is there an 80bit or 96 bit float?

- How do you access it?
Via data access, the version that includes getting at the type info?

I tried to combine Marty's suggestion for interfaces
with Andrew's suggestion to use stdint.h (int32_t etc)

instead of a enum { int8, int16, int32, ... }.

Then Andrew and Marty went on vacation, so the email list was silent
for a while.

I need to get CVS access to actually get a copy of data access
with the type info update, because I'd like to see if I can
implement what's on the Data_Interface wiki with data access.

-Kay

On Aug 8, 2005, at 15:01, Bob Dalesio wrote:

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 Ralph Lange

References:

Channel Access Client Interface Bob Dalesio

Navigate by Date:

Prev: Channel Access Client Interface Bob Dalesio

Next: RE: Channel Access Client Interface Jeff Hill

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: Channel Access Client Interface Bob Dalesio

Next: Re: Channel Access Client Interface Ralph Lange

Index: 2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024