Opencoweb

~~~~~~~~~~~
* Moderator's onSync now takes a ServerSession argument representing the client
who generated the sync event.
* All Java moderator functions have been changed to take as an argument the
client's unique ID instead of the ServerSession object.
* The Message object is also removed from Java moderator methods; instead, a Map
holds relevant information.
* An operation engine runs for each coweb session in the Python server.
* The Python server now has the concept of the moderator.
* The Python server uses Tornado 2.4 and Python 3.2.
* Removed CowebSecurityPolicy.

~~~~~~~~~~~~~
* Moderator now receives a "topic" instead of "channel" to indicate what collab
topic was affected by the sync event.
* Bots now no longer receive sync events. This was an issue since bots did not
receive transformed events. Bots can only receive private messages
from clients and broadcast messages to all clients listening. The moderator
can send private messages to bots, so the moderator can send transformed
events to bots as an alternative.
* ``SessionModeration::onServiceResponse`` was never actually used by the
server. Now, onServiceResponse is called when a bot responds to a private
message sent by the moderator. This method is not called when other clients
receive private bot message responses.
* SessionModerator now provides an ``onSessionReady()`` callback when a coweb
session becomes active (the first client joins or rejoins a previously
inactive session).
* SessionModerator methods canClientSubscribeService and
canClientMakeServiceRequest now take additional string argument specifying
the name of the service. This information is always in the message argument,
but the service name is semantically relevant and might be considered an
internal implementation detail of the message (i.e. in cases the message
format changes).
* Provide VanillaBot abstract class that implements all Bot methods (except
setProxy) with nops.

~~~~~~~~~~~~~~~

* Javascript OT engine is now a git submodule of the OCW coweb-jsoe repo. This
doesn't affect API or usage of the OCW code, but it does affect development
for OCW. Development of coweb-jsoe is separate for the coweb repo, and the
coweb-javascript/src/main/webapp/coweb/jsoe submodule needs to be updated when
coweb-jsoe is updated.
* Update to use cometd 2.5
* Moderator.onSync() now receives the topic as part of the map argument. The map
has a new key "channel" which is the bayeux channel name. See
https://github.com/opencoweb/coweb/issues/201
* Websockets is now available as a cometd transport. See
https://github.com/opencoweb/coweb/issues/207

~~~~~~~~~~~~~

* Changed Moderator API: `org.coweb.SessionModerator`_ ``getLateJoinState``
returns a ``Map`` of collab topics.
* Fixed moderator bugs.
* Fixed whiteboard cowebx-widget bug.
* Critical sections of coweb-server now correctly synchronized.

~~~~~~~~~~~

* Added :data:`cowebConfig.baseUrl` parameter to support deployments behind proxies.
* Added :data:`cowebConfig.cacheState` parameter to support turning on state caching.

~~~~~~~~~~~

* Updated the :doc:`coweb Bayeux protocol <protocol/coweb_bayeux>` to separate application operations from operation engine synchronization messages and better define the fields of a coweb event message.
* Removed the `strictJson` option from the :doc:`Python application container </python/container>` command line, making all JSON parsing strict.