faye-websocket is *just* a websocket client/server, it is a tiny slice of the Faye messaging system
Conversation
it contains only standard websocket code, not anything related to the higher-level messaging protocol, transport negotiation, etc
1
1
websocket-driver implements the websocket protocol, agnostic of I/O and concurrency. faye-websocket glues this to eventmachine
1
faye-websocket also provides some monkey-patches that provide access to the underlying TCP stream on various app servers
1
a lot of people are annoyed by the eventmachine dependency though
1
what I think rails should do: drop faye-websocket, use websocket-driver directly
1
this would let them pick their I/O/concurrency platform with no loss of power/correctness. all the protocol logic is in websocket-driver
1
Rails has the luxury of releasing a WebSocket platform in 2016. I would just demand rack.hijack support for that in their shoes
2
which would mean they wouldn't need the monkey-patches in faye-websocket. you want sockets, use a socket-compatible app server
1
a huge number of rails shops are already running websocket-driver via poltergeist, which uses it to control the phantomjs browser
2
Replying to
this particular tweet makes modern web development out to be a ghost story
it’s better that way