Recently I’ve been putting a lot of thought in to personal event networks and the need for federation between networks and the role notifications play in personal event networks. This is all part of a long journey to understand what I think of as a completely new way of individuals and organizations to interact with each other.

If you read the post example on event subscription, you know that tokens play a large role in routing the events from one network to another. I don’t think of the token as identifying the network since there’s a separate identifier for that. I’ve decided that the token represents a channel. I like that abstraction. Consequently, in the On Call TA demo, the TAs’ personal event networks subscribe to the events from the class network by supplying an event channel to the class network.

...

Tim is in charge of whether and how events are delivered. He manages the channel, delivery, and response while the publishers of these event choose the content.

Event Channels in Practice

The Sky version of EXP supports event channels. Because this capability is still beta, it has not been exposed through the normal API. To see your event channels, do the following:

1. Log into apps.kynetx.com
2. Click on your user ID in the upper right hand corner to see your profile page. The URL should look like http://apps.kynetx.com/users/<number>
3. Add /channels to that URL so that it looks like http://apps.kynetx.com/users/<number>/channels
4. Hit <return>.

You should now have an empty list of channels. Go ahead and create one and give it a name. You can create as many as you like and delete them at will.