Talk:Comparison of WebSocket implementations
![]() | Computing Unassessed | |||||||||
|
An editor has claimed that I have a conflict of interest in this page. Please see my statement here User_talk:Oberstet#Conflict_of_Interest_on_WebSockets_comparison. —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#WebSocket.
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 Wikipedia: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)
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
- 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)