Dr. In clustering, I also have a need to piggyback information with the invocation result. InvocationResult sounds like a good thing. My memory is failing, but I think CORBA does the same.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jung > , Dr. Christoph > Sent: Monday, February 18, 2002 3:21 AM > To: 'Jboss-Development ([EMAIL PROTECTED])' > Subject: AW: [JBoss-dev] Optimizing distributed transactions and > introducing InvocationResult > > > Hi, > > do not have anything useful to say to the DTC scheme proposed ... > > ... but for general consistency and future extension purposes (e.g., think > of a container extension in the form of a performance-measurement > interceptor that somehow needs to send gathered profiles to the > client where > there is a load-balancer in the client-side invocation stack ...), I�d > support the extensible (quite similar to MethodInvocation) > InvocationResult > idea. > > Also non-container exceptions should go into that representation (maybe a > subtype InvocationError for easy dispatching in the proxies?). > > Best, > CGJ > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
