This repository has been archived by the owner on Jan 7, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Changelog
Pablo Tejada edited this page Oct 27, 2013
·
8 revisions
This changelog has been implemented since v1.5.4 for earlier changes and more detailed information refer to the commit history
-
v1.6.3 - 10/27/13
- Added a new Request class in the server side to make HTTP requests
- Re-organizes the inline documentation into two modules: Server and Client
-
v1.6.2 - 10/20/13
- Added HTML5 localStorage support for storing persistent information such as a session id
- Added server side session storage. Ex: client.session.set(key, value), client.session.get(key)
- In-line documentation overhaul, included a JsDoc generated source documentation.
-
v1.6.1 - 9/22/13
- Added an APS option configurator for server side options
- Reversed the logic which tested the user names against the user define RegEx
- Added a whitelist of IPs to accept connections from
- Overhaul the demos visuals with Bootstrap 3
- The demos now have global configuration files
- Added support for extended method names. Ex: subscribe() = sub(), publish() = pub()
- New server side channel event 'restored', triggered when a user is restored back to a channel from a session prior to been timeout kicked out.
- Enhanced the Ape.log() function, it now displays properly structured objects.
- The Client.user.change() method was rename to Client.user.update() to keep consistency between server and client APIs
-
v1.6.0 - 7/07/13
- New change method in the server Ape.channel and Ape.user objects which updates a property and propagates their changes to all perspective clients
- User and Channels are now kept in sync seamlessly across clients
- Updated demos stockTicker and autoUpdate
-
v1.5.7 - 4/14/13
- New option
client.option.autoUpdate
enables user and channel properties to auto update from the server. - New client events triggered when
client.option.autoUpdate
is enabled,userUpdate
channelUpdate
- New demo to showcase the new
autoUpdate
feature and new update events, live demo - Added more inline comments throughout the source code
- New server channel event
beforeJoin
, refer to Handling Channel Events in the Server - The server
.sendEvent()
method on channel and user objects now properly handles events sent without a sender reference. - Both user and channel objects only expose public properties, making it safe to loop through the objects without including methods.
- New option
-
v1.5.6 - 4/07/13
- Fixed issue#13 enhancing the longpolling transport performance
- Added new demo payload
- Change the websocket transport keyword
wb
tows
.wb
will still work for backward compatibility butws
should be use from now on. - The global variable
userlist
in the server which holds the user list by name now isApe.userlist
- The
multi
parameter previously added has been deprecated - Enhanced client framework logging
- Enhanced and further simplify the eventPush process
- Added an event listening interface for channels in the server side. For more info Handling Channel Events in the Server
-
v1.5.5 - 3/31/13
- New user to user demo added
- Patched a potential sync event bug
-
v1.5.4 - 3/29/13
- Modified the restoration process making it it more efficient and less expensive
- The Server returns a 425 if the recipient of an event is not found
- The client framework now sends an extra parameter
multi
to determine whether the recipient is a user or channel - Attached the client version to the initial command send to the server: SERVER or RESTORE command
- Updated
eventPush
command to return error 425 in case of an unknown recipient - When creating a server module and the
sendRaw
is used to send a response to the client, event handler/listener must be prepended withraw
. Ex: sendsendRaw('Foo')
, listenon('rawFoo')