Those are good questions. I have a more fundamental problem in my application, which is that it is not really a 1-D array, it is 2-D or 3-D. CA has no mechanism for that, so I need to send the size separately anyway.
Mark
________________________________
From: Bruno Coudoin [mailto:[email protected]]
Sent: Wed 3/4/2009 3:54 PM
To: Mark Rivers
Cc: Jeff Hill; [email protected]
Subject: RE: Variable size frame
Le mercredi 04 mars 2009 à 14:56 -0600, Mark Rivers a écrit :
> I don't know about the CAS server, but in an IOC I post the array
> data first and then the size. The client waits for a monitor on
> the size, and then does a ca_get on the array. Obviously this is
> not foolproof, depending on the rates of new data and latencies but
> in practice it works well for me.
Hum, this works but its not really straightforward.
So it seems that I am not alone with this issue. Is there a plan to
enhance the protocol to make it easy.
For example, could we use the parameter 1 or 2 of the message header for
storing the payload size. Better, why do we have to send the max
possible array size in the first place and not just the actual payload
size.
Bruno.
- References:
- Variable size frame Bruno Coudoin
- RE: Variable size frame Jeff Hill
- RE: Variable size frame Bruno Coudoin
- RE: Variable size frame Mark Rivers
- RE: Variable size frame Bruno Coudoin
- RE: Variable size frame Mark Rivers
- RE: Variable size frame Bruno Coudoin
- Navigate by Date:
- Prev:
RE: Variable size frame Bruno Coudoin
- Next:
Re-wrap CaChannel based on PythonCA Wang Xiaoqiang
- 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: Variable size frame Bruno Coudoin
- Next:
New Software Engineer Position at NSCL Eric Berryman
- 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
|