directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Panicker (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRMINA-40) Filter API needs callback for enabled notification
Date Wed, 18 May 2005 06:46:26 GMT
     [ http://issues.apache.org/jira/browse/DIRMINA-40?page=comments#action_65642 ]
     
Vinod Panicker commented on DIRMINA-40:
---------------------------------------

The SSL/TLS filter needs to do a handshake when it is applied to a session and also may need
to discard sensitive data when it is being removed.  Currently this is not possible as isolated
activities because if the filter is applied on an active session, the handshake process will
not start unless any data is sent/received over the session.

Your previous comment also reminded me about something -The definition of a "Filter".  For
me, a filter is something that taps the session and monitors/modifies the data flowing over
it.  I've not been able to digest a ThreadPoolFilter.  Thats actually an implementation of
a concurrency mechanism rather than a Filter (according to my definition).  Maybe if we separate
it out into a separate entity, the problem with init() and destroy() might also be solved?

I'll have to check on the current implementation to grok what u're talking abt (filter chain
reference counting et al.). Will do that and get back to you on other possible alternatives.

> Filter API needs callback for enabled notification
> --------------------------------------------------
>
>          Key: DIRMINA-40
>          URL: http://issues.apache.org/jira/browse/DIRMINA-40
>      Project: Directory MINA
>         Type: Improvement
>     Versions: 0.7, 0.7.1
>  Environment: All
>     Reporter: Vinod Panicker
>     Assignee: Trustin Lee
>     Priority: Blocker

>
> The Filter api currently assumes that it would be applied only on unopened sessions.
 Eg - the SSL filter currently starts its work on the sessionOpened() callback.  This is an
incorrect assumption since the SSL filter could be applied on an existing plain TCP connection
as well.
> It would be great if there were new callbacks defined  - something like filterEnabled()
and filterDisabled()
> This would allow us to use the filters on existing sessions as well.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message