[CHANGED] The error argument passed into socket.onerror() is included with the error emitted to the user.
[FIXED] impermanentlyClosing to impermanentlyClosing state machine transition.
[NEW] Use channel.members.me to get the id and info for the local presence user. See the docs for more information: http://pusher.com/docs
[NEW] Send extra headers and query parameters with the private/presence channel authentication requests sent to your server. This is useful for, amongst other things, frameworks that require cross-site request forgery validation. See the docs for more information: http://pusher.com/docs
[FIXED] channel.subscribed not set to false when disconnect event occurs on the connection.
[UPGRADE] The linked version of web-socket-js. This includes a switch to the WebSocket version defined in RFC 6455. For the full list of changes in web-socket-js, see https://github.com/gimite/web-socket-js/compare/bb5797cad5244dc86410e35726ef886bbc49afe9...2ee87e910e92f2366d562efebbbec96349924df3.
[REMOVED] channel.members.add(), channel.members.remove() and channel.members.clear().
[FIXED] Mobile Safari crashing after receiving data on closed connection.
[FIXED] Attempt to transition from impermanentlyClosing to connected.
[NEW] Unit tests run twice as fast.
[CHANGED] The reconnection attempt following a dropped connection will happen a minimum of one second after the connection was previously established.
[FIXED] Calling connect after some failed connection attempts means the attempt to connect is delayed.
[FIXED] Connection closing after calling disconnect is not emitted to the developer.
[NEW] You can now unbind from an event.
[NEW] Internal errors are now logged with console.error if available. You can override this behaviour by modifying the Pusher.warn function.
[NEW] Warning logged to console.error in the following cases: no api key supplied to initialiser, authentication failure connecting to private/presence channel, attempt to connect using ws:// for application which have designated themselves as secure only, or unexpected errors returned by Pusher.
[NEW] Stale connections between the Pusher client and server are now detected and re-established.
[CHANGED] You may no longer bind to pusher_internal events.
[REMOVED] Pusher.Channel.is_private
[REMOVED] Pusher.Channel.is_presence
[NEW] Changed channel.trigger() to return a boolean indicating whether the message was actually sent.
[NEW] Private and public channels now emit pusher:subscription_succeeded events. This is consistent with presence channels.
[CHANGED] Renamed the subscription_error event to pusher:subscription_error.
[FIXED] Issue in Mozilla Firefox 8, where making a connection to non-ssl websocket endpoint from a secure page results in a security exception.
[FIXED] NetInfo listening as to not clobber the window.ononline and window.onoffline variables. Fixes issue #9.
[FIXED] Loading of web-socket-js on Mozilla browsers with MozWebSocket, issue #10.
[UPGRADE] Test framework to run in most browsers (IE6+, FF3+, Opera 11.52+, Safari, Chrome). Includes various other improvements to tests and testing infrastructure.
[NEW] Smarter SSL only error detection. If a connection is closed by pusher with an error saying that the app is in SSL only mode, then we will now force all future connection attempts to use SSL.
[NEW] Added guards around the JSON.parse calls in the Ajax Authoriser for private and presence channels.
[FIX] Fixed bug which meant that presence channels only worked correctly when user_info was supplied. It's now possible to use presence channels without specifying user_info (user_id is required).
[FIX] Fixed JSON dependency loading properly, rather than bundling it always.
[NEW] Cleverer reconnection behaviour.
If Connection is connected and the window.ononffline event is fired, this indicates that the computer has lost its connection to the local router. In response, the Connection immediately closes the socket.
If Connection is disconnected and waiting to reattempt a connection, and the window.ononline event is fired, the Connection tries to connect immediately, rather than waiting for the current waiting period to elapse.
If the window is about to attempt a connection and the window.navigator.onLine variable is false, the Connection immediately goes to the unavailable state.
Note: window.ononline, window.onoffline and window.navigator.onLine are only supported by some browsers.
[NEW] If channel authentication AJAX request returns a status code that is not 200, a subscription_error event is triggered. The subscription_error can be bound to so that the library user can respond to the failure.
[FIX] Works with IE7 again, after being broken in 1.9.0.
[FIX] Traffic Light connection status demo works in installations of Firefox 3.6 without Firebug.
[FIX] Client events triggering fixed (broken by 1.9.0)
[FIX] Removed verbose logging of internal state machine transitions
[NEW] New API to allow binding to changes in connection state. See blog post for details.
[NEW] Support for Firefox 6 native WebSocket using MozWebSocket prefix
[REMOVED] Old connection state events: pusher:connection_established, pusher:connection_failed, pusher:connection_disconnected.
[CHANGED] Socket id now accessed via pusher.connection.socket_id rather than pusher.socket_id.
[NEW] Support for Firefox 6 native WebSocket using MozWebSocket prefix
[FIX] Fix the fact that member was being added to the global scope
[CHANGE] Pusher.log function now always receives a single string argument rather than multiple arguments, making it easier to use. If you want more control, you can over-ride Pusher.debug
[FIX] When using multiple presence channels concurrently, the members object for each channel now operates as expected
[FIX] Delay Pusher initialization until document.body is defined. This fixes an issue in Firefox < 4 & IE which occasionally caused a "document.body is null" error when loading the flash fallback.
[UPGRADE] Upgraded linked version of web-socket-js. Amongst other things this removes the dependency on FABridge and reduces the minified size of fallback dependencies by 13KB. For the full list of changes in web-socket-js see https://github.com/gimite/web-socket-js/compare/6640d9d806972ea1720a273d09e8919464bcd131...bb5797cad5244dc86410e35726ef886bbc49afe9
[BUGFIX] When loaded onto a HTTPS page, load pusher dependencies from HTTPS.
[BUGFIX] Minor fix which could have allowed member_removed to be triggered with nil.
[CHANGE] Increased default connection timeout to reduce likelyhood of timeouts on first connection attempt. This is now configurable as Pusher.connection_timeout.
[NEW] Support triggering client events with new API
channel.trigger('client-myeventname', {
some: 'data'
})
[NEW] Support for new socket presence interface, and changed javascript API. The subscription_succeeded event now returns an iterator object:
presence_channel.bind('pusher:subscription_succeeded', function(members) {
members.each(function(member) {
console.log(member.id, member.info)
})
})
Also, the member object passed to member_added and member_removed now has attributes id and info rather than user_id and user_info.
[CHANGED] Improved javascript debug console logging.
[BUGFIX] When loaded onto a HTTPS page, load pusher dependencies from HTTPS [backported from 1.8.2].
[CHANGE] Increased default connection timeout to reduce likelyhood of timeouts on first connection attempt. This is now configurable as Pusher.connection_timeout [backported from 1.8.1].
[FIXED] Javascript error was raised in the case that neither native WebSockets nor Flash were available.
[FIXED] Updated linked version of web-socket-js, which fixes issue connecting from Android, allows connection attempts to timeout and retry correctly. For full details see https://github.com/gimite/web-socket-js/compare/2776dcfbf7847a5e19505432d8d63f8814e37b52...6640d9d806972ea1720a273d09e8919464bcd131
[FIXED] Pusher could fail to initialize in IE 7 & 8 when dependencies cached
[FIXED] pusher.min.js now loads minified rather than unminified dependencies.
[CHANGED] Using JBundle for bundling the distribution. This should not in any way affect the minified files, it just simplifies building them.
Wrap timeout around connections so that silently hanging connections are retried.
More robust reconnection logic, with initially shorter reconnect delay, but with increasing backoff.
Encrypted apps: apps can now be configured to connect via SSL only. There is a corresponding setting in your dashboard which will reject non encrypted connections.
var pusher = new Pusher('your-key', {
encrypted: true
})
Note that the second argument to the Pusher constructor for setting channel names has been removed. You should use pusher.subscribe instead. THIS NO LONGER WORKS:
var pusher = new Pusher('your-key', 'channel-name') # DOES NOT WORK
JSONp support for presence and private channels
Configurable transport for channel auths. JSONp allows for cross-domain channel authorization (ie. embedable widgets)
Pusher.channel_auth_transport = 'jsonp';
The default is Ajax for backwards compatibility. Ajax mode POSTS to Pusher.channel_auth_endpoint, whereas JSONp GETs.
For JSONp to work, your server must wrap the response in the callback name provided as a query parameter. Ruby example (using Pusher Gem) and Rails:
auth = Pusher[channel_name].authenticate(params[:socket_id], {
:user_id => current_user.id,
:user_info => {:name => current_user.name}
})
render :text => params[:callback] + "(" + JSON.generate(auth) + ");"
Fixed presence bug for removed duplicate members.
If I connect as the same user in different browser windows or tabs, clients should trigger remove that member from a channel's member list only when the last window/tab is closed.
See http://pusher.tenderapp.com/discussions/questions/11-presence-of-friends for discussion.
Dynamically load Javascript and Flash dependencies only for browsers that need them. Including pusher.js will:
IE: require JSON2, require and activate Flash fallback. Firefox 3.6x: require and activate Flash fallback Chrome, Safari: don't require anything. These browsers already have WebSocket and JSON support.
This saves a lot of bandwidth and makes page loads faster.
Initial Presence support. Subscribing to presence channels allows you to respond to people entering and leaving the channel in your UI, to show who is has a connection open. More documentation here: http://pusherapp.com/docs/presence.
Updated the library to use a version of the swf file hosted by Pusher. This makes it more convenient to integrate and avoids version conflicts in future.
Add some full-stack integration tests that interact with the production Pusher environment.
Trigger pusher:connection_failed if no websocket is defined, allowing the event to work on iphones etc.
- Removed switch_to_secure and switch_to_unsecure in favour of automatic failover to ssl
- Generate internal events pusher:connection_disconnected and pusher:connection_failed
- Responds to pusher:connection_established preparing for deprecation of connection_established
Added switch_to_secure() and switch_to_unsecure() to enable ssl testing
Add ability to bind events to a specific channel:
var server = new Pusher("API_KEY", "my-channel")
server.channel("my-channel").bind("my-event", function(data) {
// do something
})
Add support for subscribing to private channels. Retrieves an authentication string via Ajax from your server - for more information view the docs: http://pusherapp.com/docs/private_channels
Basic support for subscribing to multiple channels:
var server = new Pusher("API_KEY", "my-channel")
server.subscribe("another-channel")
server.unsubscribe("my-channel")
Build a single Javascript file including all dependencies for Flash fallback and browsers that don't have a native JSON implementation.
First release!