Roadmap

Future

Due in 46 days (03/22/2012)

All future features that have not yet been assigned to a version.

2%

1 closed (2%)   53 open (98%)

Related issues
  • Bug #104: Address Flash Player policy-file caching
  • Bug #285: Allow CDATA tags in all messages
  • Bug #326: Account attribute update inconsistency.
  • Bug #347: Synchronization issues when a client is joining/observing a room and room is broadcasting messages.
  • Bug #534: Notifications for changes to client attributes in RoomEvent.ADD_CLIENT listeners should occur before u6 (JOINED_ROOM) notification
  • Feature #22: Manually Request a Room Attribute
  • Feature #23: Store/Retrieve Shared Datasets
  • Feature #67: Room-qualifier scope for attributes
  • Feature #79: Auto-remove scoped client attributes on room exit
  • Feature #85: u18 (GET_NUM_CLIENTS) should take a filter
  • Feature #99: Add new UPC: SET_SERVER_UPDATE_LEVELS
  • Feature #100: Unique attribute values
  • Feature #126: Join-Room Queue
  • Feature #144: Recursion in u26 (WATCH_FOR_ROOMS)
  • Feature #150: Recursion in u21 (GET_ROOM_LIST)
  • Feature #157: Expanded Datatypes
  • Feature #195: When auto-generating a room id in create room (server and Reactor) generate within the qualifier when a qualifer is given
  • Feature #197: Add Math class operations to attribute evaluation
  • Feature #240: Determine mechanism for exposing if room is password protected.
  • Feature #242: Allow gateways to be shutdown, started and restarted.
  • Feature #279: Buddy lists
  • Feature #286: Change an attribute's options without resetting its value
  • Feature #289: Set offline acount attributes
  • Feature #296: Add clientID argument to JOIN_ROOM (u4) and LEAVE_ROOM (u1) UPCs
  • Feature #307: Add pagination to WATCH_FOR_ACCOUNTS (u98)
  • Feature #335: Allow clients to receive updates at scheduled intervals rather than deltas every change.
  • Feature #339: Account observation should include attribute changes for offline users
  • Feature #348: Change UPC to a binary protocol
  • Feature #352: Add security limit to room-scoped client attributes
  • Feature #354: Expose all attributes to admin clients
  • Feature #355: Sanction clients that violate security rules
  • Feature #356: Prevent flooding and denial of service attacks
  • Feature #408: Attribute privacy and permissions
  • Feature #409: Improve client/room metadata management
  • Feature #415: Decide whether to require password when changing a room's password
  • Feature #416: Ban notification
  • Feature #417: Provide access to ban "reason"
  • Feature #456: Turn management.
  • Feature #478: Add assignedRoomID argument to CREATE_ROOM_RESULT (u32)
  • Feature #483: Post Union load tester on unionplatform.com
  • Feature #510: Binary BLOBs as attribute values and message arguments
  • Feature #525: Add restart room UPC.
  • Feature #526: Secure restart room UPC.
  • Todo #257: Implement TERMINATE_SESSION UPC support
  • Todo #322: Discuss how outside datasource should integrate in to Union.
  • Todo #323: Determine how to give out temporary access to Union
  • Todo #341: Implement keyboard-safe record separator (remove pipe)
  • Todo #398: Move all UAP messages into UPC spec
  • Todo #425: Add additional cause information to RoomEvent REMOVE_CLIENT.
  • Todo #453: Document port 80,443 setup
  • Todo #549: Audit UPC results for missing PERMISSION_DENIED status.
  • Idea #17: Room Occupant Roles
  • Idea #35: Defining Applications within the Server
  • Idea #152: Stealth mode for a client