Darryl and I had a long discussion about heartbeat in Matahari yesterday. I'll try to hit on the major points. The first thing towas discussed was that Matahari should only have one heartbeat timer. I'm only mentioning this now because it was a point of confusion in the past. If an instance of Matahari has multiple "subscribers", those subscribers will get heartbeats at the same interval. That said, we discussed the API for setting/getting heartbeat interval. This value would turn out to be a property of Matahari itself. Our thinking is that we shoud implement 2 API calls: heartbeat_interval_set (int interval); heartbeat_interval_get (); We also discussed whether Mahari should immediately begin sending heartbeats when it starts or if there is really a nead for API calls like: heartbeat_start (int interval); heartbeat_stop (); Obviously there is some overlap with heartbeat_start and heartbeat_interval_set. Is there a compelling reason to use start/stop API calls rather than just automatically begin sending heartbeats when Matahari starts? In addition to the API calls that will call into Mathari, we proposed a client-side API call that will register a callback to be called when a heartbeat is received. This would be completely optional. An alternative for checking health would be to check the timestamp of the last heartbeat received and verify that it was received within a certain threshold (ie. a more passive way to check health as opposed to registering a callback). Thoughts? Comments are welcome/encouraged. Ryan