Skip to content
Commits on Nov 22, 2010
  1. @mloughran

    Version bump to 0.7.0

    mloughran committed
  2. @mloughran
  3. @mloughran

    Assign default port number for encrypted connections

    mloughran committed
    * Net::HTTP isn't smart enough to default to 443
Commits on Nov 5, 2010
  1. @mloughran

    Added SSL support

    mloughran committed
    * Currently not doing certificate verification
    * Optional - configure with Pusher.ssl = true
    * Stop memoizing Pusher.url - it makes things rather inflexible
  2. @mloughran
Commits on Oct 29, 2010
  1. @mloughran

    Simplify specs for trigger_async by using webmock

    mloughran committed
    * Specs require a tiny change to signature
Commits on Oct 28, 2010
  1. @mloughran
Commits on Oct 7, 2010
  1. @mloughran
  2. @mloughran
  3. @ismasan

    Added source to Gemfile

    ismasan committed
  4. @mloughran
Commits on Aug 9, 2010
  1. @ismasan

    Version bump to 0.6.0

    ismasan committed
  2. @ismasan
  3. @ismasan
  4. @ismasan

    Renamed data key to :channel_data so it's less confusing (because it …

    ismasan committed
    …arrives to the server inside another :data hash)
  5. @ismasan

    Pusher::Channel#authenticate(socket_id, custom_data)

    ismasan committed
    * JSON-encodes custom data, adds it to signature and returns in the format:
    {:auth => auth_string, :data => json_encoded_custom_data}
    
    USAGE (Rails example):
    
    response = Pusher['my_channel'].authenticate(params[:socket_id], {:user_id => @user.id})
    render :json => response # => (calls to_json on it)
Commits on Aug 6, 2010
  1. @ismasan

    Pusher::Channel#socket_auth takes an optional string and adds it to t…

    ismasan committed
    …he auth signature
    
    * So users can add extra data to response (ie. presence user info). These data should be authenticated as well. Presence channels will expect the data to exist in a the params so they can compare with the passes auth and secret.
  2. @ismasan
  3. @ismasan

    I need to assert that the Gem works with newest em-http, but I know i…

    ismasan committed
    …t breaks the specs. For now I'll allow it to use newer versions.
  4. @ismasan

    Froze version of em-http-request, as newer versions break the specs. …

    ismasan committed
    …TODO: fix specs to work with newest and make sure the actual gem does too?
  5. @ismasan
Commits on Jun 1, 2010
  1. @mloughran
  2. @mloughran
  3. @mloughran

    Version bump to 0.5.3

    mloughran committed
  4. @mloughran
  5. @mloughran
Commits on May 25, 2010
  1. @mloughran
  2. @mloughran

    Version bump to 0.5.2

    mloughran committed
  3. @mloughran

    Updated changelog

    mloughran committed
  4. @mloughran
  5. @mloughran
  6. @mloughran
  7. @mloughran
  8. @mloughran

    Moved require statements that were in the wrong place - in particular…

    mloughran committed
    … uri was being required too late
Commits on May 20, 2010
  1. @olly
Something went wrong with that request. Please try again.