> Anyway, the point that I wanted to make in the explanations is that the structure information is exchanged only at connection time.
Absopositively. The protocol, https://github.com/epics-base/pvAccessCPP/wiki/protocol, exchanges the structure information at the start of a get/put/monitor....:
When the data is then exchanged, it's based on bitfields to indicate which piece of the structure follows, then just the raw data.
Even the initial structure exchange is optimized.
Like "timeStamp" is only described once as
structure #47 = timeStamp { long seconds, int nano, ..}
Later, the server would just send "type 47" over the existing TCP connection, since the client remembers that type 47 = { long seconds, ...}.
-Kay
- References:
- pvData introduction Timo Korhonen via Core-talk
- Re: pvData introduction Kasemir, Kay via Core-talk
- Re: pvData introduction Timo Korhonen via Core-talk
- Re: pvData introduction Kasemir, Kay via Core-talk
- Re: pvData introduction Timo Korhonen via Core-talk
- Navigate by Date:
- Prev:
Re: pvData introduction Timo Korhonen via Core-talk
- Next:
Re: pvData introduction Johnson, Andrew N. via Core-talk
- 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: pvData introduction Timo Korhonen via Core-talk
- Next:
Re: pvData introduction Johnson, Andrew N. via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|