Hotwireの感想 - laiso
Hotwire https://hotwire.dev/ Turboを中心としたウェブアプリケーションのアーキテクチャの要素技術やコンセプトをPRするための名称 Hotwireというライブラリがあるわけではない 役割としてはMicro FrontendsとかReactのlearn once, write anywhereなどに似ている アプリケーション実装言語非依存だけど現状Railsアプリケーションしか実用できる基盤がない Hotwireの思想 アプリケーション開発者の生産性を上げることを目的にしていること サーバーサイド言語でフロントエンドを実装したいアレではなかった プログレッシブ(段階的に利用可能)であること 必要な技術だけを使い無駄なことをしないことで効率化する Hotwireが列挙する技術は1つづつ有効にできる クライアントサイドでViewを差分更新する現在の主流のシングルペー
Real time push messaging | Fastly Documentation
Push messaging allows events that occur on servers to be pushed to end users without the user having to refresh or request an update. There are several types of push messaging, suitable for different use cases. Using Fastly for real time messaging reduces load on your origin servers, allows messages to be routed efficiently to large numbers of clients, and offers extremely low latency.
WebSockets for Ruby made easy
WebSockets for Ruby made easy Easy WebSockets + Powerful Publish / Subscribe Iodine (with or without Plezi) offers easy WebSockets and a powerful pub/sub solution for Ruby. Add iodine to your favorite Framework or use it directly for a Rack application: require "iodine" # this config.ru example runs on iodine. # A simple Websocket Callback Object. module BroadcastClient # subscribe to new clients.
The dark side of the Rack and Websockets dreams
There’s a dark side to Ruby web applications. One thing is clear – real time web applications in Ruby are hurting. We can argue a lot about who it is that allowed themselves to succumb to the dark side. Some argue that Rails are derailing us all and others that socket.io, Faye and node.js are eating away at out sanity, design, performance and feet… but arguing won’t help. As I pointed out in an is
Create a Chat App with Rails 5, ActionCable, and Devise — SitePoint
Rails 5 has introduced a bunch of new great features, but one of the most anticipated ones is of course ActionCable. ActionCable seamlessly integrates WebSockets into your application and offers both client-side JS and server-side Ruby frameworks. This way, you can write real-time features in the same styles as the rest your application, which is really cool. Learn more on ruby with our tutorial S
Rails 5.0.0rc1 Released - Is ActionCable Ready for Prime Time?
Lets commit these changes: $ git add . $ git commit -am “Add rooms/message views” Now open up http://localhost:3000 again and see what we’ve got: What we have here is a basic rails app with our test message rendered. This is Rails 101. Just about the simplest possible app. With ActionCable it’s just as simple to add realtime functionality, so lets do it: 6. Generate a ActionCable channel with a ‘s
Real-Time Rails: Implementing WebSockets in Rails 5 with Action Cable
Resources What is Heroku? Help Customers Careers Events Podcasts Compliance Center Heroku is for Developers CTOs Team Collaboration Startups Enterprises Agencies Students See More Languages Node.js Ruby Java PHP Python Go Scala Clojure See More Latest News from the Heroku Blog Heroku Blog Find out what's new with Heroku on our blog. More news View all blog posts It's been one year since Action Cab
Surrogate WebSockets Alongside Rails
ActionCable is coming to Rails 5 and brings with it the promise of using WebSockets directly in Rails. Ruby has a notoriously bad concurrency story, and that certainly extends into the realm of WebSockets and pubsub. ActionCable may be suitable for a small number of authenticated sessions, but scaling persistent connections to thousands or tens-of-thousands won't be easy. That's all right, the bea
Ruby & WebSockets: TCP for the Browser - igvita.com
By Ilya Grigorik on December 22, 2009 WebSockets are one of the most underappreciated innovations in HTML5. Unlike local storage, canvas, web workers, or even video playback, the benefits of the WebSocket API are not immediately apparent to the end user. In fact, over the course of the past decade we have invented a dozen technologies to solve the problem of asynchronous and bi-directional communi
rubyでwebsocketを試してみる - Qiita
require 'em-websocket' require 'pp' connnections = [] EM::WebSocket.start({:host => "0.0.0.0", :port => 8888}) do |ws_conn| ws_conn.onopen do connnections << ws_conn end ws_conn.onmessage do |message| pp message connnections.each{|conn| conn.send(message) } end end ※ポートを8888で起動します ※pp messageでサーバに送られてきたメッセージを標準出力します ※connnectionsに接続を格納し、connnections.eachで接続されたクライアント全てに メッセージを返すようにしています <html> <hea
TwitterのChirpUserStreamsをWebSocketで垂れ流す - 準二級.jp
Twitter の ChirpUserStreams を WebSocket で垂れ流して閲覧できるアプリを作りました！WebSocket 対応ブラウザ(Chrome 等)でお楽しみください！WebSocket すごい！ユーザ体験が変わる！ ChirpUserStreams => WebSocket ボク @june29 と @kei_s から見た世界を体験できるようにしてあります。ChirpUserStreams については、以前にエントリを書きました。 TwitterのChirpUserStreamsをごくごくしてみた 本家の API がベータ版であり、まだまだ不安定なので、たまにスクリプトの再起動をかけたりしながら動かしています。見てみたいけど「なんにも表示されないよ？」って方がいたら、@june29 や @kei_s に話しかけてみてください。対応できるかもしれません。 User
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Real-time Rails: Foundations for a Better ActionCable
GitHub - palkan/litecable: Lightweight Action Cable implementation (Rails-free)
GitHub - anycable/anycable: AnyCable for Ruby applications
Building a Rack Web Server in Ruby
GitHub - Kilobyte22/webrick-websocket: A simple gem implementing websockets on the WEBrick web server
GitHub - igrigorik/em-websocket: EventMachine based WebSocket server