> I propose that we add dbr_ulong_t and dbr_ushort_t to the CA client API.
> Requests for these types would of course be refused when they are
> issued to old servers.
Of course the problem here is that some existing clients will not be prepared
to handle new native data types that were not in the original API. This
would not be backwards compatible. Perhaps the solution is to add a routine
to the client API that disables backwards compatible promotion when the
new types are installed. This routine would only be called only by clients that
have
been properly updated so that they are able to handle the new native types.
Backwards compatible promotion would be moved to the client lib when the new
data types are installed.
Jeff
- Navigate by Date:
- Prev:
RE: change in promotion of types from database to channel access Jeff Hill
- Next:
Re: change in promotion of types from database to channel access Chip Watson
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
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: change in promotion of types from database to channel access Chip Watson
- Next:
Re: change in promotion of types from database to channel access Ned Arnold
- Index:
1994
1995
1996
<1997>
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|