You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Steve Graham <sg...@us.ibm.com> on 2000/12/19 14:06:35 UTC
Re: Sanjiva's walkthrough at F2F (was: Requirements - 2000/12/11)
Yuhichi:
<sgg></sgg>
Yuhichi wrote:
>Steve and James,
>It seems difficult for me to follow the discussion, but ...
>In F2F, Sanjiva drew a behavior of the engine as follows:
> TransportListner--(invoke)-->Engine--(invoke)-->ChainContainer -->
>(Sorry, I am not sure if I remember it correctly.)
<sgg>at the highest level view, it looks pretty much like what we worked up
during the session </sgg>
>According to me, Engine should be called Repository (or Contianer pool)
>which manages multiple ChainContainers to forward incoming request
>one of them.
<sgg>In OO speak, I believe an engine HASA chainContainerRegistry (and a
handlerRegistry) but I don't believe an Engine ISA registry. </sgg>
>Is the conclusion you had along this idea? Otherwise, I am happy if you
>(esp. Steve) map your idea to the engine behavior we drew.
>Yes, even ChainContainers are pluggable, so you may invoke a
>payload processor without ChainContainer if you do not need any
>header processing.
<sgg>It may be as you say, no chainContainer, or perhaps a chainContainer
that is "empty". Functionally the same, but the "empty" chainContainer
avoids an exceptional situation in the architecture. Probably
implementation detail. There will most likely always be a chain container,
first, the global one (derived from global WSDD). Second, the dispatcher
(pluggable provider to) that invokes the target web service is a handler.
At least that is the current thinking and we need to understand Yuhichi's
ISSUE better.</sgg>
> Furthermore, to me, Repository (Engine in the
>above figure) is also pluggable. Therefore, if you do not need
>lifetime management etc., you just invoke ChainContainer or
>payload processor directly.
>Thoughts?
<sgg>I had not imagined the registry (repository) itself would be
pluggable. I had imagined that the registry is a simple lookup table,
potentially with some sort of pluggability at the persistence layer.
Perhaps the class which implements the registry interface is configurable
in the engine. I had imagined that alot of the lifecycle management would
happen at the chainContainer level (ie something more specific to the
target web service itself, and therefore could understand the target web
service's lifecycle scope as deployed). The chainContainer could do
lifecycle management by how it implements the invoke() method (ie on invoke
(), it delegates invoke() to one of a pool of chains, or delegates invoke()
to the chain associated with the session (based on some session
identification derived from the Message object).</sgg>
<sgg>As clarification, when you use the term "payload processor", are you
referring to the object we have been calling dispatcher, pluggable
provider, pivot point, etc.?</sgg>
<<attached emails in discussion chain snipped>>