Events

Config

<config>
	<!-- default duration in seconds to keep a message for -->
	<default-ttl>30</default-ttl>

	<!-- default duration in seconds to keep a GET:events/ operation alive when no messages are present -->
	<default-wait>10</default-wait>
</config>

Message

A message can be any valid XML document.  Every message is tagged with a sequential eventid and eventdate (Beryil and later).  If the following document is posted to the Events service.

<ticker>
	<symbol>GE</symbol>
	<price>32.82</price>
</ticker>

It will be sent to listeners as:

<ticker eventid="42" eventdate="2006-05-22T01:16:03.0716064Z">
	<symbol>GE</symbol>
	<price>32.82</price>
</ticker>

MessageList

<list maxeventid="42" eventdate="2006-05-22T01:16:03.0716064Z">
	<ticker eventid="42">
		<symbol>GE</symbol>
		<price>32.82</price>
	</ticker>
</list>

Subscription

<subscription>
	<uri>http://localhost/myService/myListener</node>
</subscription>

GET:events/

GET:/

POST:events/

Add a message to the list of messages.  If any listeners are waiting or if subscribers are present, notify them about the new message.

POST:/

Add a message to the list of messages.  If any listeners are waiting or if subscribers are present, notify them about the new message.

POST:subscribe/

Adds a subscriber to the Events service.  By default, a new subscriber only receives messages that are sent after the subscription has been established.  However, by providing the after query parameter, this behavior can be changed to return all message in the Event service that occurred after the specified eventid, but before the subscription was established.

POST:unsubscribe/

Removes a subscriber from the Events service.  This operation succeeds regardless if the specified subscription has established a subscription or not.