On Thu, Sep 10, 2009 at 04:11:28PM -0700, Steven Dake wrote:
IMO the proper way to do this is to ensure whatever ringid was delivered in
a callback to the application is the current ring id returned by the api.
This gets rid of any races you describe above.
I can't really think of any races
On Fri, 2009-09-11 at 10:41 -0500, David Teigland wrote:
On Thu, Sep 10, 2009 at 04:11:28PM -0700, Steven Dake wrote:
IMO the proper way to do this is to ensure whatever ringid was delivered in
a callback to the application is the current ring id returned by the api.
This gets rid of any
On Mon, Aug 31, 2009 at 02:28:33PM -0700, Steven Dake wrote:
On Mon, 2009-08-31 at 15:44 -0500, David Teigland wrote:
Here are two related and troublesome problems that would be nice to fix,
probably in future versions -- they probably can't be fixed maintaining
existing apis and protocols
Here are two related and troublesome problems that would be nice to fix,
probably in future versions -- they probably can't be fixed maintaining
existing apis and protocols (although adding new api's to help with them might
be nice if possible).
1. correlating events from different services
On Mon, Aug 31, 2009 at 02:28:33PM -0700, Steven Dake wrote:
On Mon, 2009-08-31 at 15:44 -0500, David Teigland wrote:
Here are two related and troublesome problems that would be nice to fix,
probably in future versions -- they probably can't be fixed maintaining
existing apis and protocols
