Event References

Event references identify an event handled by ENS. Event references use the following URI syntax (as specified by RFC 2396):

scheme://authority resource/[?param1=value1&param2=value2&param3=value3]

where:

• scheme is the access method, such as http, imap, ftp, or wcap.

  For Calendar Server and Messaging Server, the ENS scheme is enp.

• authority is the DNS domain or host name that controls access to the resource.

• resource is the path leading to the resource in the context of the authority. It can be composed of several path components separated by a slash (“/”).

• param is the name of a parameter describing the state of a resource.

• value is its value. There can be zero or more parameter/value pairs.

In general, all Calendar Server events start with the following:

enp:///ics

The Messaging Server notification plug-in iBiff uses the following scheme and resource by default:

enp://127.0.0.1/store

Although the event reference has a URI syntax, the scheme, authority, and resource have no special significance. They are merely used as strings with no further interpretation in ENS.

Calendar Server Event Reference Example

The following is an example event reference URI to subscribe to all event alarms with a calendar ID of jac:

enp:///ics/alarm?calid=jac

This URI is not meant to be used by end users.

Messaging Server Event Reference Example

The following is an example event reference that requests a subscription to all NewMsg events for a user whose user ID is blim:

enp://127.0.0.1/store?evtType=NewMsg&mailboxName=blim

When using ENS with Messaging Server, the user ID you specify is case sensitive.

This URI is not meant to be used by end users.