While working on rsrv/camessage.c, I've noticed a curious discrepancy
between the header preparation code in cas_copy_in_header() and the
protocol document at
http://epics.cosylab.com/cosyjava/JCA-Common/Documentation/CAproto.html
In section 3.1 we are told that the maximum short form payload length is
0x4000 bytes, but in the code the maximum generated payload length appears
to be 0xFFFE bytes.
Presumably, as this code has been in use for quite a long time, the
protocol document is in error, or perhaps is a little unclear? As I read
it, the document is saying that the extended header must be used for
payloads longer than 0x3ff0.
Also, presumably, the statement that extended headers cannot be used for
short payloads is unecessarily restrictive?
- Replies:
- RE: EPICS protocol header Jeff Hill
- Navigate by Date:
- Prev:
[PATCH 4/4] Drive-by refactoring in caserverio.c Michael Abbott
- Next:
[PATCH 3/4] Add autosizing array support for caget and camonitor. Michael Abbott
- 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: Hacking rsrv/camessage.c Jeff Hill
- Next:
RE: EPICS protocol header 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
|