m_serLoc is 0 in buffer from SocketReadTask #2780
Unanswered
zimri-leisher
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I'm curious as to why the
SocketReadTask
sets theBuffer::m_size
variable on receiving data but not theBuffer::m_serialize_repr::m_serLoc
variable. This is not a big problem because it's easy to do:buf.getSerializeRepr().setBuffLen(buf.getSize());
It just tripped me up before I understood what was going on because when I call
Buffer::getSize
, it tells me I have plenty of bytes, but then when I calldeserialize
it tells me I have none. Is the idea that the dev should completely manage the state of theSerializeBufferBase
class?Beta Was this translation helpful? Give feedback.
All reactions