You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Sasha Dolgy (JIRA)" <ji...@apache.org> on 2011/02/18 19:37:38 UTC

[jira] Updated: (VYSPER-266) Abstract org.apache.vysper.xmpp.state.resourcebinding.ResourceRegistry

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

Sasha Dolgy updated VYSPER-266:
-------------------------------

    Attachment: DefaultServerRuntimeContext.java.patch

> Abstract org.apache.vysper.xmpp.state.resourcebinding.ResourceRegistry
> ----------------------------------------------------------------------
>
>                 Key: VYSPER-266
>                 URL: https://issues.apache.org/jira/browse/VYSPER-266
>             Project: VYSPER
>          Issue Type: Improvement
>          Components: roster and subscription
>    Affects Versions: 0.6
>            Reporter: Sasha Dolgy
>            Priority: Minor
>              Labels: resourceregistry
>         Attachments: DefaultServerRuntimeContext.java.patch
>
>
> Converting org.apache.vysper.xmpp.state.resourcebinding.ResourceRegistry into an interface as to enable developers to create different implementations for the ResourceRegistry.  For example, I am curious to see how the ResourceRegistry will behave using Apache Cassandra as a backend.  

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira