Experimental Physics and Industrial Control System
Subject: |
Re: V4 design issue: Should primitive data types have well defined precisions? |
From: |
Ralph Lange <[email protected]> |
To: |
[email protected] |
Date: |
Wed, 22 Jun 2005 15:35:01 +0200 |
I completely agree with Benjamin:
CA should have size-fixed types on the network,
DA should support the native types of its language and convert from/to
the CA types as necessary.
Ralph
Benjamin Franksen wrote:
According to DA philosophy the interface should /not/ enforce how
clients or servers store /their/ data.
[...]
Yes, at some point we will have to nail down CA network format. I
suggest that primitive types for the network layer should be as rich
as possible, /including/ unsigned types. Since each data transfer is
initiated (originally) by the client, communication with a native Java
client will simply never use those unsigned types, thus creating no
problem for the native client. A native Java server, OTOH, will never
expose unsigned data, so a client cannot request it, thus still no
problem.
Cheers,
Ben
- References:
- RE: Puts Dalesio, Leo `Bob`
- V4 design issue: Should primitive data types have well defined precisions? Marty Kraimer
- Re: V4 design issue: Should primitive data types have well defined precisions? Marty Kraimer
- Re: V4 design issue: Should primitive data types have well defined precisions? Benjamin Franksen
- Navigate by Date:
- Prev:
Re: V4 design issue: Should primitive data types have well defined precisions? Benjamin Franksen
- Next:
Re: hello world examples 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
2025
- Navigate by Thread:
- Prev:
Re: V4 design issue: Should primitive data types have well defined precisions? Benjamin Franksen
- Next:
Re: hello world examples 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
2025