Permalink
Commits on Feb 17, 2011
  1. Release version 0.8.0

    mloughran committed Feb 17, 2011
  2. Allow Net::HTTP errors to be easily rescued, and change README to sug…

    mloughran committed Feb 17, 2011
    …gest using `trigger!`
    
    * Rescues Net:HTTP errors and re-raises as Pusher::HTTPError in Channel#trigger!
    * The original error is avaiable as http_error.original_error
    * Use WebMock more extensively in tests
  3. Release version 0.7.1

    mloughran committed Feb 17, 2011
Commits on Feb 14, 2011
  1. Increase the timeout for trigger_async requests from 2 to 5s

    mloughran committed Feb 14, 2011
    * This should be configurable since it depends on your network and location
Commits on Nov 22, 2010
  1. Version bump to 0.7.0

    mloughran committed Nov 22, 2010
  2. Assign default port number for encrypted connections

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

    mloughran committed Nov 5, 2010
    * Currently not doing certificate verification
    * Optional - configure with Pusher.ssl = true
    * Stop memoizing Pusher.url - it makes things rather inflexible
Commits on Oct 29, 2010
  1. Simplify specs for trigger_async by using webmock

    mloughran committed Oct 29, 2010
    * Specs require a tiny change to signature
Commits on Oct 28, 2010
Commits on Oct 7, 2010
  1. Added source to Gemfile

    ismasan committed Oct 7, 2010
Commits on Aug 9, 2010
  1. Version bump to 0.6.0

    ismasan committed Aug 9, 2010
  2. Renamed data key to :channel_data so it's less confusing (because it …

    ismasan committed Aug 9, 2010
    …arrives to the server inside another :data hash)
  3. Pusher::Channel#authenticate(socket_id, custom_data)

    ismasan committed Aug 9, 2010
    * 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. Pusher::Channel#socket_auth takes an optional string and adds it to t…

    ismasan committed Aug 6, 2010
    …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. I need to assert that the Gem works with newest em-http, but I know i…

    ismasan committed Aug 6, 2010
    …t breaks the specs. For now I'll allow it to use newer versions.
  3. Froze version of em-http-request, as newer versions break the specs. …

    ismasan committed Aug 6, 2010
    …TODO: fix specs to work with newest and make sure the actual gem does too?
Commits on Jun 1, 2010
  1. Version bump to 0.5.3

    mloughran committed Jun 1, 2010