directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Fellars (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRMINA-54) ProtocalSession begins reading(decoding) before the session has been opened
Date Tue, 07 Jun 2005 21:16:00 GMT
    [ http://issues.apache.org/jira/browse/DIRMINA-54?page=comments#action_12312938 ] 

Daniel Fellars commented on DIRMINA-54:
---------------------------------------

Thanks Trustin,

>From initial testing, I now get the sessionCreated called first, so I do all my initialization
there before any decoding occurs.  

For clarification, what would be the difference between the sessionCreated and sessionOpened,
would there be times when sessionOpened is called and not sessionCreated?

Thanks for you speedy reply on this great product.


Dan

> ProtocalSession begins reading(decoding) before the session has been opened
> ---------------------------------------------------------------------------
>
>          Key: DIRMINA-54
>          URL: http://issues.apache.org/jira/browse/DIRMINA-54
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.7.1
>  Environment: windows xp using TCP/IP
>     Reporter: Daniel Fellars
>     Assignee: Trustin Lee
>      Fix For: 0.7.2

>
> With a local connection, I have seen it over the network but not as often, MINA regularly
will call the Decoder.decode(..) method before it calls ProtocolHandler.sessionOpened
> Inside the decode, I use the protocolSession attachment, which is set in the ProtocolHandler.sessionOpened
> so on these occassions, i am unable to read properly because my attachment object is
not available.
> I have an ugly hack for my needs that requires synchronizing on the protocolsession in
both methods, but would think that MINA should properly manage the lifecycle to gaurantee
that sessionOpened is always called before any read/writes on the protocolsession.

-- 
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