I hadn't even considered collecting traces/spans in this way yet, and have taken the approach of "stuff outputting logs in JSON format to stderr/local file". I usually end up writing a (temporary, structured) log message with the relevant span tags, but wouldn't it would be much better to run the actual trace/span code and be able to verify it locally without the ad-hoc log message? The prototype I built is a web... - Source: Hacker News / 8 months ago
I also used to use this (http://websocketd.com/) along with netcat(1) before just biting the bullet and writing my own websocket library for our server as we needed to scale up slightly. Source: about 1 year ago
Http://websocketd.com/ (Runs command line C or C++ programs as websocket programs, similar to inetd / CGI). Source: over 2 years ago
Do you know an article comparing websocketd to other products?
Suggest a link to a post with product alternatives.
This is an informative page about websocketd. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.