I believe we shouldn't impose a fixed sync/async way of working on the users of the remote api. I also think that usng a method param to change to async invocation is cumbersome for most users. So, perhaps we should create a sync CommandService and an Async CommandService? I'm also in favour of using EJB3. Since the commandservice normally is behind the service interfaces ... why not use a modern and cool implementation where everybody loves to work with? EJB3 runs today on all app servers I'm aware of (JBoss, Glassfish, Oracle, IBM, ...). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236925#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...