Experimental Physics and Industrial Control System
Hi,
In the CAS server, vector variable are always sent at their maxBound
size instead of their real size as found in the user's provided gdd.
This has 2 consequences:
- We loose bandwidth transferring trailing zeros when the vector is not
fully populated.
- On the client side, there is no way to determine where the data
stops in the vector.
Digging in the code I found out that in
casStrmClient::readNotifyResponse the message size is based on
msg.m_count which is set to maxBound. Don't desc.getDataSizeElements()
should be used instead.
Am I doing something wrong or this is a bug ?
--
Bruno Coudoin
http://gcompris.net Free educational software for kids
- Navigate by Date:
- Prev:
Re: record processing delay Andrew Johnson
- Next:
ca_put with non base type Bruno Coudoin
- 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: record processing delay jun-ichi.odagiri
- Next:
RE: CAS server and partial vectors Bruno Coudoin
- 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