mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Fondermann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (VYSPER-336) is the status change right?
Date Fri, 07 Jun 2013 21:28:20 GMT

     [ https://issues.apache.org/jira/browse/VYSPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bernd Fondermann resolved VYSPER-336.
-------------------------------------

    Resolution: Fixed

fixed the state change to 'interested'
                
> is the status change right?
> ---------------------------
>
>                 Key: VYSPER-336
>                 URL: https://issues.apache.org/jira/browse/VYSPER-336
>             Project: VYSPER
>          Issue Type: Bug
>            Reporter: wan jian ming
>            Assignee: Bernd Fondermann
>
> in ResourceState, there is code like:
>  public static ResourceState makeInterested(ResourceState inState) {
>         if (inState == AVAILABLE )
>             return AVAILABLE_INTERESTED;
>         return CONNECTED_INTERESTED;
>     }
> so when one session in AVAILABLE_INTERESTED state, can call this function again (client
reload will send iq message, and this function will be called), it will return to CONNECTED_INTERESTED,
is it right?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message