Talk:Comparison of WebSocket implementations

An editor has claimed that I have a conflict of interest in this page. Please see my statement here User_talk:Oberstet. —Preceding undated comment added 14:49, 21 September 2011 (UTC).

With regard to the other objections raised, please see my comment on the objecting editor's talk page User_talk:AlistairMcMillan.

Oberstet (talk) 07:46, 23 September 2011 (UTC)


 * Since the changes to the websocket protocol versions 8-13, the HLL Websocket Server is one of the few (maybe the only for a while) with an actual live demonstration using the updated protocol, which has now been submitted to become the actual standard. There are very few experts on websockets at this point. It's new technology, and unlike movies, there's not a lot of people out there to review.

Further, above editor has removed the following list of implementations, first from the WebSocket page, because it would be "an invitation to spam" and violates the WP:LINKFARM policy. Then, after I moved the list to this page - adding the comment that they should be included into the comparison page over time - above editor removed it also from this page, pointing to NOT.

I disagree:


 * the mere links to WS implementations is already useful information to i.e. developers wanting to learn/deploy WS
 * having the list at least temporary on this page, to encourage people to do further work and include it into the comparison table with detailed feature-wise information is even more useful
 * denying Wikipedia user information by blindly following "policies" to the letter is not helpful

Oberstet (talk) 07:46, 23 September 2011 (UTC)

Further I assume that it is not vandalism or the like to include the deleted list now at least on this talk page for users to discuss.

Should you happen to know the details for one of those implementations, please consider including it into the comparison table.

Oberstet (talk) 07:46, 23 September 2011 (UTC)

The main page just has a particular type of "notable" websocket implementation, however there are many other uses for it, for example in Embedded world to provide realtime UI in browser. I am the author of libwebsockets, like the other deleted ones here it's certainly going to be of interest to certain people looking for lightweight, embedded websockets and not, as the page currently has, just browsers and big iron solutions. Maybe it means there should be another table or another page? Warmcat1 (talk) 10:07, 9 May 2013 (UTC)

Deleted Implementations
My organization has been evaluating WebSockets strategies for some upcoming initiatives, and the previous version of this page had been of great use to us by providing information on a large number of libraries and giving test results from the Autobahn test suite - a de facto standard for WS implementations. Additionally, some of the libraries that have been removed from this page are notable in the tech community, namely libwebsockets, websocketpp, and Autobahn. The recent modifications are destructive. Can we roll them back?

Acanaday (talk) 20:57, 6 June 2013 (UTC)

I should add that the current version of the page is neatly informational, but useless in the extreme to serious developers looking to try out different WS implementations. Additionally, some of the implementations might not be as notable as say Firefox, but they are targeted at smaller markets. A C Websockets implementation targeted towards embedded devices is not going to accumulate the internet notoriety of some of these other systems. Despite this, if you're doing embedded development, or light-weight high-performance development, none of the items on this list are of any good to you.

Spud111 (talk) 08:47, 11 October 2013 (UTC)

I re-inserted Lightstreamer in the comparison, and actually I didn't understand the reason why it has been deleted. If 'notability' (as mentioned in the article edit comments) was the problem, I can't see the point, as it has its own Wiki page (which has been linked now) and is a known solution. I didn't found other guidelines and admission criteria than this, so I assumed it should properly belong this page. If there is a specific reason why it shouldn't be added I'll be glad to discuss about it. Thanks

Other Implementations
Other implementations that should be included in above detailed comparison over time.


 * Stargate - WebSocket support for Pyramid, a Python web framework
 * Node-WebSocket-Server - a server-side implementation for Node.JS (deprecated)
 * ws - a server-side implementation for Node.JS
 * em-websocket - a server-side implementation for EventMachine Ruby
 * CoreWebSocket Core Foundation based WebSocket library for iOS and Mac OSX by Mirek Rusin
 * UnittWebSocket Objective-C Client Objective-C WebSocket library for iOS (supports rev00, rev07, rev08, rev10, binary & text messages, message fragments, etc)
 * UnittWebSocket Java/Server Client Java IO/NIO WebSocket client/server libraries for Java/Android (supports rev07, rev08, rev10, binary & text messages, message fragments, etc).
 * weberknecht Java WebSocket library for Android
 * Cramp - Ruby/EventMachine based server implementation for WebSocket and Server-Sent Events
 * JBoss Netty – asynchronous event-driven Java New I/O (NIO) network application framework supporting WebSockets
 * Webbitserver – A Java event based WebSocket and HTTP server
 * Union Platform – JavaScript-extensible Java server and JavaScript WebSocket client library for creating connected applications
 * Alchemy Websockets – Lightweight microthreaded C# WebSocket server and client library
 * Misultin – Erlang library for building fast lightweight HTTP(S) servers, which also supports websockets.
 * Grizzly - Java Server and Client code with support for multiple websocket draft versions
 * GlassFish - Java Enterprise Edition application server that exposes Grizzly's websocket implementation for use in EE applications
 * Cowboy - Small, fast and modular Erlang HTTP server implementing all browser-supported websocket protocol versions — Preceding unsigned comment added by Oberstet (talk • contribs) 07:39, 23 September 2011 (UTC)
 * libGeminiSocket - .NET application Server implementing websocket draft version and hight level Javascript client library — Preceding unsigned comment added by 82.60.95.246 (talk) 11:04, 18 March 2012 (UTC)
 * MigratoryData WebSocket Server – An enterprise-grade WebSocket server supporting up to 1 million concurrent users on a single entry-level server (benchmarks)
 * libwebsockets - Pure C nonblocking client and server library suitable for embedded, very small code and per-connection footprint, CMake based build system, compatible with crossbuild — Preceding unsigned comment added by Warmcat1 (talk • contribs) 09:59, 9 May 2013 (UTC)

---

The information here is pretty old. Especially for Firefox I see Firefox 8... We are Firefox 13 guys... At least a flags should be set to inform the reader that this is NOT anymore a page "to make choices" because it is obsolete. — Preceding unsigned comment added by 89.19.84.15 (talk) 21:49, 12 July 2012 (UTC)