On Jul 7, 2006, at 9:04 AM, Meeraj Kunnumpurath wrote:

Jeremy,

Ok, having a brief look at the JCA work manager API, these are my
thoughts

1. The high-level API are very similar, a manager and optional support
for listeners for callbacks 2. There are subtle differences between the
actual semantics of work allocation. JCA work manager supports both
blocking (doWork), asynchronous (scheduleWork) , blocking
start/asynchronous completion (startWork), whereas a JSR 237 it is
always asynchronous (scheduleWork). JSR 237 supports a different
semantic for blocking calls using wautForAll and waitForAny.

Do you have any thoughts on what features you want to support in the
API.

We know we need async so that is probably the best place to start. If people need sync then they can support it with a blocking listener; if enough people need sync then we can add that to the API later (to allow passthrough to JCA which may be more efficient).

Sound reasonable?
--
Jeremy

PS I'm on IRC if that helps (irc.freenode.net#tuscany)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to