penenin commented on pull request #2121: URL: https://github.com/apache/thrift/pull/2121#issuecomment-624138820
I think I confused things with my comments above. The linker error I encountered was in D on Linux. To try to clarify, this is what I have done and where I am at: - I manually tested my code on Windows by modifying the C++ tutorial server and the nodejs tutorial client. I bundled the client using Webpack and was able to communicate from Firefox and Chrome to the tutorial server over WebSockets. - I opened the PR and was asked to provide tests. - On Linux, I modified the C++ cross language test server, nodejs test client, and js test client to add websockets and accept websocket as a command line argument. - None of the tests work. When I look at the generated network traffic with Wireshark, I don't see the WebSocket handshake like I expect. - Then still on Linux, I recreated my modified C++ tutorial server and Webpacked tutorial client. Those don't work either and I don't see the WebSocket traffic in Wireshark like I would expect. - I then tried to modified the D tutorial server on Linux to test WebSockets in order to see if I was running into a Linux platform issue or if there was a difference in behavior between the two language libraries. That is where I ran into the linker error I don't see in Windows. Setting aside the last point about D as off-topic since this is a C++ PR, the only thing I can think of is that I am running into some difference between the Linux and Windows socket implementations, or that there is some sort of compression going on that I am not aware of (even though I have tried to turn off per message deflate). Since my Linux development experience is very limited, the biggest hurdle I am running into is trying to get a good debugging environment set up or just even knowing roughly what I should be looking for. I have been struggling with plain command line gdb. Based on your suggestion, using CMake, I am trying to get the cross language tests set up and building on Windows, but I am running into build issues there as well. I can update the PR with the failing tests if you would like to take a look at what I have. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
