[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Moving core o.j.invocation classes to common

[bstansberry@jboss.com]

Thanks for adding me.

"scott.stark at jboss.org" wrote : 
  | These would need to be a legacy unified invoker artifact in a remoting subproject.
  | 

Where were you thinking this legacy artifact would be used? In 5.0.x, the new model is going to be used on the server side, so obviously not there.

Tom mentioned you'd expressed interest in backporting the new stuff to 4.0.  In 4.0 I imagine the new model could be an alternative for the client side.  But don't see how it could used be on the server side w/o breaking any existing custom interceptors people have written.  So, if in 4.0 org.jboss.invocation is the server-side model, don't know why we'd move it to remoting.

Only thing I could think of is in 5.0.x having some special proxy factories that could create a proxy that used the old model, and then a special invoker that could translate the call using the old model into the new model for use inside the server. A transition aid for people with custom client interceptors/load balance policies.  But, well, yuck :(

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971678#3971678

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971678