[
https://issues.apache.org/jira/browse/GEODE-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251937#comment-17251937
]
ASF subversion and git services commented on GEODE-8532:
--------------------------------------------------------
Commit 8b0a5dc4294316241d6cbfce62a03dad10e1d18c in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=8b0a5dc ]
GEODE-8532: parse chunked responses in gnmsg tool (#702)
- basic chunk handling works
- output is just message type and chunk length for each chunk
- Need to handle chunked responses coming back from simultaneous connections
- Conceivably these can come back out-of-order, so logging the 'this' pointer
for the connection allows parsing code to disambiguate
> Parse chunked replies in gnmsg tool
> -----------------------------------
>
> Key: GEODE-8532
> URL: https://issues.apache.org/jira/browse/GEODE-8532
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> As a native client developer, I would like to be able to see all reply
> messages from server to client when debugging with gnmsg. I can, in fact,
> see replies/responses when they come back in a "complete" message, but at
> present when a response is "chunked" gnmsg ignores it, so things like, for
> example, `getAll()` responses don't show up in the message dump. This is
> probably a complex task, and may require logging more data for chunk
> responses in the C++ native client code, but it's important.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
