- From: Tom Rutt <tom@coastin.com>
- Date: Sat, 12 Jun 2010 19:13:00 -0400
- To: public-ws-resource-access@w3.org, Tom Rutt <tom@coastin.com>
I would like to put a new proposal g on the table for discussion to resolve the ws-man heartbeat requirement. This is a modified version of proposal d, the difference is that the verify notification is send a number of times indicated in the count input parameter, at the regular interval indicated in the interval input parameter , where the parameters are part of the optional verify element of the getStatus request. The verify notification is sent during the requested interval /count regardless of how many other notfications have been sent on the subsription. This simplifies the specification, and implementation, in that there is no need for the event source to have knowledge of the last event sent on the subscription. This was one of the main objections voiced for option d. The objection to heartbeat was you could not turn them off when you don't need them. Sending a getstatus with a count of 0 would turn off the verify notification sequence. When the sinc feels unconfortable about the status of the event delivery capability, it can send a getstatus with an interval and count appropriate to its current paranoia level. I do believe that this warrants another proposal for consideration. It is significantly different than the current proposal d. Tom Rutt -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133
Received on Saturday, 12 June 2010 23:13:23 UTC