David Jencks wrote:
The latter is completely out of the question performance-wise, so I hope Ole is not argueing for it.4) invocation is routed to correct transport mechanism (such as by the HA Invoker interceptor)(AFAIK not yet written as an interceptor) 5) Invocation is received at server side. 6) The server decides if the resource registration callback is needed.And the resource registration occurs on the return of the original method invocation, or does it take an extra round trip immediately? The former incurs redundant bookkeeping requirements and the latter is inefficient.
It seems that sending the resource registration request on the return of the original method invocation should not be any more complex than what David does right now. In fact, there would still have to be a client side interceptor that takes the tx registration info from the InvocationResponse and perform the registration with the client side's TX manager. IMHO, David's approach is simpler to understand and cleaner than passing registration back in the InvocationResponse object.
Anatoly.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
