…individual application processes directly. Each application process can now be accessed through its own TCP socket port. The port numbers are randomly allocated by the operating system and the protocol is plain HTTP, so you can use existing tools like ‘curl'.
We take security very seriously. These sockets are bound to 127.0.0.1 so it's not possible to access them from remote computers. Furthermore, each socket is protected by its own unique randomly generated secure password. One …
- 赖洪礼的 blog: Phusion Passenger for Python?
- : Munin Graphs for Phusion Passenger (a.k.a. mod_rails)
- duck_punching: Passenger (mod_rails) for development. Now with debugger!
- Ruby Inside: Vagrant: EC2-Like Virtual Machine Building and Provisioning from Ruby
- Brightbox Blog: Ubuntu 10.04 LTS "Lucid" now available
- 4 Lines of Code: Continuous Integration for Ruby on Rails
…Phusion Passenger Lite can listen on a Unix domain socket instead of a TCP socket, just like Thin and Unicorn. In reverse proxy setups this can yield much higher performance than TCP sockets.
Advantages over existing reverse proxy app servers
Unlike Mongrel, Thin and Unicorn, Phusion Passenger Lite can dynamically spawn and shutdown processes according to traffic. However you can also configure it to use a static number of processes! In fact you can configure a minimum and a maximum …
- The Queue Blog: Link dump for July 1st
- A Rubyist Railstastic Adventure: The Road to Passenger 3: Technology Preview 3
- 赖洪礼的 blog: Phusion Passenger for Python?
- Ruby Inside: New Relic RPM Officially Supports Rack and Sinatra - Finally!
- duck_punching: Passenger (mod_rails) for development. Now with debugger!
- Hackido: Moving to Ruby Enterprise Edition
error handling and ACK timeout: if a subscriber doesn't ACK a message after a (message-specific) timeout, the message will be sent to another subscriber. Messages are also resent automatically if a subscriber dies and its connection expires.
topic subscriptions (messages broadcast to all subscribers) with prefix matching
support for high numbers of subscriptions: millions of subscriptions pose no problem
simple extensions within the STOMP protocol to report the number of messages …
- 4 Lines of Code: Background Jobs in Ruby on Rails
- Litany Against Fear: Messaging with Ruby on Rails Notes
- ronin coder: Open Source Bridge presentation
- Jake Scruggs: Rails Conf 2010 Day 2
- Alexey Kovyrin's Blog: ActiveMQ Tips: Flow Control and Stalled Producers Problem
…is a protocol agnostic ( layer 3 ) proxy, which allows us to intercept any TCP data stream and manipulate it at will .
So, instead of talking directly to Beanstalk, all the traffic is routed through our custom em-proxy (~150 LOC) which parses the Beanstalk protocol, intercepts custom commands, or simply inspects the "delay" parameter, and decides where the job should be routed: beanstalk or the MySQL instance. Jobs that are scheduled at least one hour into …
- 4 Lines of Code: Background Jobs in Ruby on Rails
- A Fresh Cup: Double Shot #576
- Rubynaut: Install ruby memcached on MacOSX
- Rails Envy » Home: Rails Envy Podcast - Episode #099
- techno weenie: Structuring your background jobs
- Scout ~ The Blog: Three reasons for Resque (and a Scout Plugin)
…Websockets are part of the specification for HTML5, and are essentially long-running native TCP connections in the browser. These allow a client to establish a connection to a server, and have immediate feedback when there are events they need to be notified of. Websockets make your applications more dynamic, and break them out of the traditional stateless request-response cycle. Your applications can therefore rely on maintained state in the browser which will be kept fresh with messages …
- has_many :bugs, :through => :rails - Home: Websockets made easy with Cramp
- igvita.com: Ruby & WebSockets: TCP for the Browser
- Bamboo Blog: Brain Dump of Real Time Web(RTW) and WebSocket
- paperplanes: A Collection Of Redis Use Cases
- Luke Redpath: Pushing events to your iPhone using WebSockets and Pusher
- Ruby on Rails Podcast: RailsConf Europe - Ruby on Rails Podcast
…single request. This is probably a good thing, since allowing instances to persist between requests would open a can of data integrity, thread safety, and multi-host worms. But I can't shake this vision I have of a sort of in-process memcache for Ruby objects, where multiple processes communicate changes to each other via TCP wormholes... Does anyone else share this vision, or am I doomed to wander the Ruby blog desert, mumbling incoherently at strangers?
- a work on process: Friday (ish) links - January 15th 2010
- without_scope - Home: Flexible ActiveRecord Versioning with ActsAsRevisable
- NetManiac: Are ActiveRecord validations worth anything?
- flow: named_scope - start using it!
- Complicated Simplicity: The Dark Side of Duck Typing
- oldmoe: Building the Never Blocking Rails, Making Rails 12X Faster
- Persistent Connections - so you don't have to create a new TCP connection for every request --- keepalive=onC
- Caching
- how do you decide when something is stale?
Jeff Casimir - Ruby Processing
- dynamically generate images in ruby app
- uses jruby
- first built to create verticle column headers
- Distributed Programming with Ruby -> to learn how to send jobs to ruby processing from rails
- Beanstalkd -> simple fast background processing -> brew …
- omgbloglol: The Path to Rails 3: Approaching the upgrade
- Jason Seifer: 32 Rack Resources to Get You Started
- Intridea - Company Blog: Rack Middleware and Rack Applications: What's the Difference?
- techno weenie: Ruby 1.9 on Heroku
- Orlando Ruby Users Group: Meeting Thursday May 13th
- codahale.com: When Formality Works
…being generated by your LINQ queries. Silverlight 4's TCP Sockets Video It's part of Mike Taulty's 8-part series on networking with Silverlight. S. Somasegar's Key Software Development Trends
(I covered it in this article ) It's interesting to see what Microsoft's brain trust sees as important, and it's also good to see testing treated as a first-class citizen. Gesturecons , …
…hooked-up to the server by a persistent, firewall-safe, bidirectional TCP connection. The server can send data to the browser at any time, via predefined callbacks, while talking back to the server is as straight-fordward as: socket.send( "Thank you, Mr. server!" );
Think about it for a moment. You've just upgraded your browser to a Real-Time, Hyper-Responsive Information Device ( RTHRID . I'm sure it's going to catch on). All that without leaving the comfort …
- Bamboo Blog: The JS model layer
- Bamboo Blog: Custom event emitters in Javascript
- : Sammy.js, CouchDB, and the new web architecture
- Mental Paging Space: ActiveJquery - Status
- AdaRuby: Quest for The Fluid Web Framework
- ronin coder: For all our sakes
…of threads being woken up sending some 60.000 packets (there may be some buffering taking place on TCP side merging multiple sends but still)
I guess this scenario is just not really caught any developer attention yet as it should be rather easy to optimize. Same as network cards are designed to throttle numbers of interrupts they get and process several packets at the time we could make replication threads to be woken up in the batches. For example we could tune the system to wake up the …
- A Fresh Cup: Double Shot #625
- Global Nerdy: Apress' "Windows Azure Platform"...and Discounts!
- Tammer Saleh: Master May I?
- Alexey Kovyrin's Blog: Rails Developer for a Large Startup: My Vision of an Ideal Candidate
- SD Ruby Podcast: Episode 041: MySQL Clustering