[Authentication] Async API vs. Immediate

Stef Walter stef-list at memberwebs.com
Fri Oct 30 13:26:56 PDT 2009

Stef Walter wrote:
> So at this point, it looks like we need to decide something pretty
> fundamental about our API. We need to decide whether we're going to have
> operations that don't complete immediately, or whether we try to design
> the API without that. This has primarily to do with prompting.
> There are two approaches, each has drawbacks. The term 'operation' below
> is used to describe an action requested by the client which changes
> state in the service and can: a) fail b) be canceled.


No comments?

Well to be honest I'm not super keen on either solution. But if nobody
else has any input, and nobody else has another workable/implementable
idea, I'll need to make a decision so I can get on with things.

I'm leaning on the side of the 'long running operations' approach [1].
For me, what tips the scale is the fact that it allows maximum
flexibility in the future.



[1] For more details see 'Approach Two: Dbus Async calls + cancellation'
in the lower half of this email:

More information about the Authentication mailing list