EnigmaTriton commented on PR #3144: URL: https://github.com/apache/thrift/pull/3144#issuecomment-2896703615
Hello @CJCombrink, I don’t know if you were using the same language on both client and server side (I’m guessing so) but in this case, there is a way to determine which end is not translating correctly to/from the network encoding: perform a network capture to analyze with Wireshark. Your assumption that C++, Go, and .NET show the correct implementation is right and 00112233-4455-6677-8899-aabbccddeeff is indeed how Wireshark should display the data on the network capture. Hope it helps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@thrift.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
