On Jul 28, 2005, at 09:15, Marty Kraimer wrote:
2) For network accesssable data a key requirement is to define a set
of primitive types that can be widely supported.
..
primitive data types: bool, octet, int16, int32, int64, float32,
float64
Whether we need locked types or not should have a firm answer.
Many applications don't care about the exact data type.
A plotting or math tool tries to get every property as 'double'.
Probe will display a dialog that says "type = int32",
but then it'll still display everything as a 'string'.
On the other hand, the archiver could save disk storage by
storing int16 as such and not double.
In order to handle every current and future type,
it could use an octet interface to the data,
treating the data as a black box.
So only 'octet array' would have to be a fixed type.
The gateway, on the other hand, needs to understand the data,
so that it can send updates to different clients using
different deadbands.
This mean we have to nail the basic types down.
Or would the gateway only fan data out to multiple clients
if they use the same subscription request (filter, events),
so that the gateway can treat the data as an octet array?
-Kay
- Replies:
- Re: primitive data types, was: ICE and TIPC Ralph Lange
- References:
- RE: ICE and TIPC Jeff Hill
- Re: ICE and TIPC Marty Kraimer
- Navigate by Date:
- Prev:
RE: String Interfaces Jeff Hill
- Next:
RE: ICE and TIPC 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:
Re: ICE and TIPC Marty Kraimer
- Next:
Re: primitive data types, was: ICE and TIPC 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
|