> From: Leo Sutic [mailto:[EMAIL PROTECTED]]
>
> > >>> 2) removal of release()
> >
> > -1
>
> -1 for now, but I have had a discussion off the list with
> Robert Mouat, that I believe has resulted in a replacement
> for release(). As soon as I get Robert's permission to post
> our exchange on the list I'll do it.
:) Combine a unique ComponentManager with my session proposal,
and you can reclaim a component in mid processing--and have
another instance finish processing. The point is that the
session object maintains the important information.
But, you could always discourage the use of pooled *components*,
and have individual components manage the scarce resources.
> > The problem, as Peter showed, is when I "hint" for a SSL
> > connection. If I get a normal connection, I *can* still
> > connect, but I *don't* want
> > it. In this case, the /hint/ is mandatory and cannot be overlooked.
>
> Seems like you're looking for a different ROLE, then:
>
> interface SSLConnectionManager extends ConnectionManager {};
>
> or is that too bulky?
Actually that would be the best thing.
However, some things like the Transformer selection is not as hard
and fast. All the pipeline knows is it needs a transformer. The
pipeline doesn't really care if it is an XSLT based transformer,
a transformer that reads informatin from a database and inserts
new elements, or some other custom transformer.
The hint is a way of saying I need transformer X.
Anyway, I want a satisfactory solution for these situations.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
