Change log

Reactor 1.0 Alpha 1

04/25/2009

The first public release.

  • Todo #108: fix documentation links to moock.org

Reactor 1.0 Alpha 2

06/08/2009

  • Bug #164: ConnectionMonitor should always provide default settings
  • Bug #168: Statistics: fix overflow error in byte-counter
  • Feature #153: Auto-recover from lost connection during client setup
  • Feature #163: UConnection: make some config file options optional
  • Feature #165: ConnectionMonitor: add getters to allow access to current monitor settings
  • Feature #167: NumericFormatter: add UTC version of time-formatting methods
  • Feature #170: SocketManager should provide feedback on security failures

Reactor 1.0 Alpha 3

08/03/2009

  • Bug #201: Fix client attribute evaluation
  • Bug #206: Improve auto-reconnection
  • Feature #173: Client-to-Server Module Messages
  • Feature #191: Client count for a qualifier should include "unique clients" and "total occupants"
  • Feature #199: ClientManager: add getClientByAttribute()
  • Feature #200: Expose client ID during room attribute updates
  • Feature #203: Automatically try backup connections on connection failure
  • Feature #205: Add VersionNumber class for easy version comparisons
  • Todo #202: Rename UConnection to Reactor
  • Todo #204: Refactor SocketManager to XMLSocketConnection

Reactor 1.0 Alpha 4

09/06/2009

  • Bug #227: Room's sendMessage() throws an error on null message arg
  • Bug #228: Client's getAttribute() method parameter order change
  • Bug #231: Remove Tokens.SERVER_ONLY
  • Bug #232: ClientManager's getAttributeForClients() method parameter order change
  • Todo #207: Validator should be updated to match latest UPC specification

Reactor 1.0 Alpha 5

11/01/2009

  • Bug #252: Move setReadyTimeout() from ConnectionMonitor to ConnectionManager
  • Bug #253: Failure to receive client ready (u63) should cause ConnectionManager to move to next connection
  • Feature #250: Communicate over HTTP
  • Feature #251: Add ConnectionManagerEvent, separate from ConnectionEvent

Reactor 1.0 Alpha 6

12/20/2009

Reactor 1.0 Alpha 7

04/11/2010

  • Feature #110: Add ClientEvent.OBSERVE_ROOM and ClientEvent.STOP_OBSERVING_ROOM
  • Feature #262: Log should display milliseconds to three digits
  • Feature #268: Add isObservingRoom() to IClient
  • Todo #302: Revise Room object management code

Reactor 1.0 Beta 1

10/14/2010

  • Bug #385: fix isWatchingForClients and isWatchingForAccounts on disconnect
  • Bug #387: Fix Client connection state reporting
  • Bug #388: ConnectionMonitor: fix isPingShared()
  • Bug #389: Connection should clear sessionID on client-side disconnect
  • Bug #390: HTTPConnection should ignore attempts to send HTTP requests when disconnected
  • Feature #368: Add PERMISSION_DENIED status to UPC message handlers
  • Feature #386: Add getUpdateLevels() to Client

Reactor 1.0 Beta 2

03/23/2011

  • Bug #372: Exception in Reactor's dispose() method
  • Bug #373: Exception on multiple sequential connect() calls
  • Bug #420: AccountManagerEvent.CREATE_ACCOUNT_RESULT event does not trigger on ACCOUNT_EXISTS
  • Bug #427: Account observation bug
  • Bug #461: Attempting to login to account B when already logged in to A yields ALREADY_LOGGED_IN
  • Feature #287: Reactor should provide an api to modify room settings
  • Feature #384: Add a ban-client API
  • Feature #411: Add an "add/remove moderator role" API
  • Feature #413: Add an API for retrieving a room's settings

Reactor 1.0 Release

04/26/2011

  • Bug #463: Make Room's sendModuleMessage()'s messageArguments parameter optional
  • Bug #470: Send message to client: listener argument-mismatch errors fail silently

Reactor 1.0.2

06/26/2011

  • Bug #486: Setting "auto reconnect frequency" to -1 does not stop any existing reconnect timer in progress
  • Bug #500: Null reference in MessageManager's notifyListener()
  • Feature #475: Add clear module cache command
  • Feature #476: Add ServerModuleListSnapshot
  • API Change #496: Renamed RoomModuleType to ModuleType

Reactor 1.1.0

10/16/2011

  • Bug #511: MessageManager does not remove all listeners on disconnect
  • Bug #513: Connection affinity should not apply to connections that have timed out before becoming ready
  • Bug #514: When no valid connections are found, ConnectionManager should start at beginning of connection list
  • Bug #515: ConnectionManager should dispatch failure when disconnect() terminates in-progress connection
  • Bug #530: ConnectionMonitor reconnects before application listeners receive connect-failure notification
  • Feature #506: Make HTTP-request retry delay configurable
  • Feature #516: Add auto-reconnect attempt limit
  • Feature #554: Add UPC message monitoring-and-statistics API

Future

Pending Review

Reactor 2.0.0 Beta 1

  • Bug #566: ConnectionMonitor should not attempt to reconnect if it has been disposed
  • Bug #567: CoreMessageListener's u103 (CLIENT_REMOVED_FROM_SERVER) listener throws error on custom clients
  • Bug #568: Rooms that have been disposed should abort subsequent disposal and purge-data requests
  • Bug #601: UPCProcessingRecord fails to unescape CDATA
  • Bug #603: RoomSnapshot's getNumObservers() and getNumOccupants() return the wrong values
  • Bug #604: Room observers not removed in core UPDATE_LEVELS_UPDATE listener
  • Bug #609: Disposal does not halt room synchronization
  • Feature #596: Add a ReactorEvent.CONNECT_REFUSED event
  • Todo #607: Disable auto-reconnect on CONNECTION_REFUSED