mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Mahoney (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (VYSPER-297) Accept client suggested resource names
Date Wed, 05 Oct 2011 05:24:34 GMT

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

Mike Mahoney updated VYSPER-297:

    Attachment: vysper-297-2.patch

I've made some additional changes to BindIQHandler.java. It now handles the three conflict
policies outlines in http://xmpp.org/rfcs/rfc6120.html#bind-clientsubmit-error-conflict. 
The third scenario is more complicated than the first two, so any feedback on the implementation
is welcomed.

The second patch is a complete patch for VYSPER-297.  The first patch file can be ignored.
> Accept client suggested resource names
> --------------------------------------
>                 Key: VYSPER-297
>                 URL: https://issues.apache.org/jira/browse/VYSPER-297
>             Project: VYSPER
>          Issue Type: Task
>          Components: connection handshake
>            Reporter: Mike Mahoney
>            Assignee: Bernd Fondermann
>         Attachments: vysper-297-2.patch, vysper-297.patch
> Modify Vysper so it will accept a client's suggested resource name at during resource
binding.  This includes performing a ResourcePrep on the suggested name and checking it for
size (0-1023 characters).  It should also limit the maximum number of resources that can be
bound to a single bare JID.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message