<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
<br>
I've taken Bob's application services document, made some changes to the
interface, and recast it in the format used in our other design documents.
This part will be included in the main venues design document, but I wanted
to send it separately to simplify review. <br>
<br>
Bob: Mostly, I made the following changes:<br>
<ul>
<li>the data channel is not a web service; therefore, applications do not
register with the data channel for particular event types</li>
<li>an application object is created with a single data channel, instead
of relying on the application to create the data channel(s) it needs; at
this point, I only see the need for one data channel; the AppObject.CreateDataChannel
method has been removed</li>
<li>the application object does not assign a public_token to components;
instead, the public_id in the ClientProfile will be used</li>
<li>we only have one application type, so there is no application service/factory
to create them</li>
</ul>
I need to make the existing implementation conform to this spec very soon,
so let me know if you have any comments.<br>
<br>
Thanks,<br>
<br>
Tom<br>
<br>
</body>
</html>