cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Re: [PROPOSAL] Client and Conduit changes
Date Thu, 22 Mar 2007 19:23:59 GMT
On 3/19/07, Johnson, Eric <Eric.Johnson@iona.com> wrote:
>
> So currently all the Client, and the JAX-WS Dispatch, do in terms of
> messaging duties is wire the interceptor chain together, pass messages
> to the interceptor chain, and receive messages that are pushed back up
> the interceptor chain?
>
> It is the Conduit and transport level code that is responsible for doing
> all of the correlation work?



If that is true, I'm -1 on Dan's proposal. Eoghan's concerns about
> seperation of concerns is well placed. While it makes writing a
> transport thornier, it is the transport layer that owns the thorns.


Well for the deocupled case the Conduit doesn't really need to do much
correlation. I don't really see many thorns there that need to be
encapsulated.

- Dan

-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message