Handling Groove Web Services Events

Applies to: SharePoint Workspace 2010 | Visual Studio 2008

Groove Web Services provide a mechanism for monitoring Groove events generated by changes in the underlying data. These changes can be initiated by the user on the client system providing the Web Services, by another user in a workspace, or by the application itself.

The process of monitoring Groove events involves three stages:

  1. Establishing subscriptions.

    You create one or more subscriptions to listen to event sources of interest. Events meeting the subscription definitions are sent to an event queue. Subscriptions can be created using GrooveSubscriptions.Create or CreateAggregated2. Both operations send events to a queue you define. The difference is that Create defines a single event source while CreateAggregated2 aggregates all events of a particular class emanating from a collection of sources.

  2. Reading events.

    Periodically you poll the queue. You can use GrooveEvents ReadSummary to get the state of the queue and determine if any events of interest have occurred. You can then get detailed information using GrooveEvents Read and ReadExtended operations.

  3. Deleting the subscription.

    When you no longer need to monitor events, you delete the subscriptions using GrooveSubscriptions.Delete. It is important to delete unneeded subscriptions, because a subscription uses resources as long as it is active, regardless of whether or not the initiating Web services application is running.

In This Section

Groove Web Services Events

Groove Event Listening Model

Creating Subscriptions in Groove Web Services

Reading Groove Web Services Events

Deleting Subscriptions

See Also


GrooveEvents Web Service

GrooveSubscriptions Web Service


Accessing the Groove Web Services Hierarchy