Gearing up for a new Juggernaut

October 30th, 2006

Juggernaut is almost ready for its next release. I’ve added the latest version to the svn in the hope that people will have the chance to test it (and catch any potential problems).

New features are:

  • Authentication
  • Event-Machine push server
  • General clean up (mainly javascript.

Things I want to get into the next release:

  • Actionscript reconnection (after a specified amount of seconds).
  • Update readme

The major issue with this (sub) version is lack of support for IE (it comes up with some obscure javascript error). Hopefully this will get sorted in the next couple of days. It works in Firefox and Opera.

Authentication is done via a http request to rails from the push server, containing the client concerned session id. Rails checks the session id and sends an appropriate http response code, like so:

def auth
 if session[:user_name]
  render :nothing => "true"
  headers["Status"] = "Unauthorized"
  render :text => "Could't authenticate you",
                          :status => '401 Unauthorized'

This is not for the weak hearted… :)

Juggernaut | Comments | Trackback Jump to the top of this page

3 comments on “Gearing up for a new Juggernaut”

  1. 01

    I look forward to this next release. I’ve been very interested in trying Juggernaut out for some time now.

    beppu at November 7th, 2006 around 1:03 pm
    Jump to the top of this page
  2. 02

    I ran into an error while trying to use the svn version that I checked out last night. I threw together your sample app (I’ve written some stuff using the first release of Juggernaut) and when I submitted the form the push server crashed with this error. Infinitely repeatable, btw.

    Starting to parse line buffer
    nope, didn’t dispatch request
    Connection closed
    Starting to parse request
    /usr/local/lib/ruby/gems/1.8/gems/json-0.4.2/lib/json.rb:373:in `parse_object’: unexpected token in object at ‘channels: [”chat”], ‘! (JSON::ParserError)
    from /usr/local/lib/ruby/gems/1.8/gems/json-0.4.2/lib/json.rb:256:in `parse’
    from /usr/local/lib/ruby/gems/1.8/gems/json-0.4.2/lib/json.rb:498:in `parse’
    from script/push_server:199:in `parse_request’
    from script/push_server:163:in `dispatch_request’
    from script/push_server:158:in `unbind’
    from /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:776:in `event_callback’
    from /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:201:in `run_machine’
    from /usr/local/lib/ruby/gems/1.8/gems/eventmachine-0.7.0/lib/eventmachine.rb:201:in `run’

    Josh Adams at December 16th, 2006 around 9:14 am
    Jump to the top of this page
  3. 03

    Are you sure you’re doing:
    require ‘rubygems’
    require ‘json’

    maccman at December 27th, 2006 around 5:36 pm
    Jump to the top of this page

Leave a Reply


You can keep track of new comments to this post with the comments feed.

19yr old hacking away at Ruby on Rails and Flex