search

WardCunningham / Smallest-Federated-Wiki

This wiki innovates by: 1. federated sharing, 2. drag refactoring and 3. data visualization.
http://wardcunningham.github.com/
GNU General Public License v2.0
1.21k stars 178 forks source link

Sinatra Websocket Gem #284

Open hallahan opened 12 years ago

hallahan commented 12 years ago

I have found a library that should be suitable for integrating WebSocket into the Sinatra project:

https://github.com/simulacre/sinatra-websocket

Looking at the example project, it seems to function in an easy to use mannor, and it uses vanilla WebSockets.

I tried to import it, however, I get this error when I attempt to do bundle install:

Bundler could not find compatible versions for gem "thin": In Gemfile: sinatra-websocket (>= 0) ruby depends on thin (~> 1.3.1) ruby

thin (1.4.1)

I am not an expert with bundler and gems, so I am not sure how to fix this. The project works fine by itself, and when i do gem list, It shows the actual thin to be 1.4.1, and this appears to meet the requirement that this error is listing.

What is going on here?

Here's the 2 lines I did in attempt to include this library:

https://github.com/hallahan/Smallest-Federated-Wiki/commit/6771865a1e343c9f144921c266328bd3d64afb14

donpdonp commented 12 years ago

"~>" means allow the version to be greater than or equal to 1.3.1 in the last digit only. So 1.4 is "too new".

WardCunningham commented 12 years ago

What would be the better thing to say?

Best regards -- Ward

Sent from my mobile 503-432-5682

On Sep 12, 2012, at 6:24 PM, Don Park notifications@github.com wrote:

"~>" means allow the version to be greater than or equal to 1.3.1 in the last digit only. So 1.4 is "too new".

— Reply to this email directly or view it on GitHub.

donpdonp commented 12 years ago

">= 1.3.1" should take care of it.

hallahan commented 12 years ago

Unfortunately that version specification is with the sinatra-websocket gem. I'm thinking if we are to get this to work, we have to actually pull in websocket-sinatra into the project or somehow modify that gemfile.

The good news is that I took a look at SockJS, and it works rather well with the Express project. It turns out we can have our cake and eat it too regarding the use of web-sockets and being backwards compatible with browsers that do not support it. SockJS falls back on XHR but uses the same WebSocket standard API. So far, I'm liking it more that socket.io. There is also a Ruby server implementation that is currently under development. Right now I'm leaning towards updating the Express with the search functionalities and going with that.