On Mon, May 18, 2009 at 7:55 PM, Gary Mazz <span dir="ltr">&lt;<a href="mailto:garymazzaferro@gmail.com">garymazzaferro@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
 From the current discussions, there has been no mention of events. Will<br>
the occi support events ? What will the model look like ?<br>
</blockquote><div><br>This is something I had thought about a little but not considered a focus point for us. I did however consider the possibility of OCCI messages being long lived in that they can be queued and passed over transports like XMPP (this was one of a number of potential use cases for signatures).<br>
<br>The interest in doing this would be, for example, a client that has rendered a number of resources and wants to know about state changes and the like. They would just need to subscribe to the resource and when the state changes they would be sent the updated entry. Similarly an management system could ask for regular updates of e.g. performance monitor counters.<br>
<br>Does this sound adequate for your needs or do you have use case(s) that require more - and if so, why aren&#39;t they in the wiki ;)<br><br>Sam<br><br></div></div>