Niels Berglund continues his series on R Services internals:
What happens is that straight after the
AuthenticateConnection
you will hit theWriteAsync
breakpoint twice, the same way as we see in Code Snippet 4. The first hit atWriteAsync
sort of makes sense, as it ties up with the call-stack we see in Code Snippet 5. But what about the secondWriteAsync
(the one that causes the second package to be sent), where does that come from? To try to figure that out, we start with the call-stack for that particularWriteAsync
.Execute the code in Code Snippet 1 again, and continue to the second
WriteAsync
. When you hit the breakpoint do akc
again. The call-stack should now look somewhat like this (this time it is the full call-stack):
It’s interesting the kind of stuff you can find with Wireshark and a debugger.
Comments closed