Changes

Jump to navigation Jump to search
1,704 bytes added ,  08:59, 3 March 2015
Line 45: Line 45:  
* '''Mentor:''' Kevin Smith, Tobias Markmann
 
* '''Mentor:''' Kevin Smith, Tobias Markmann
 
* '''Contact Details:''' Chatroom at swift@rooms.swift.im
 
* '''Contact Details:''' Chatroom at swift@rooms.swift.im
 +
    
=== Openfire New Protocol support ===
 
=== Openfire New Protocol support ===
Line 61: Line 62:  
* '''Mentor:''' Dave Cridland <dave@cridland.net>
 
* '''Mentor:''' Dave Cridland <dave@cridland.net>
 
* '''Contact Details:''' XEP-0045 chatroom at open_chat@conference.igniterealtime.org
 
* '''Contact Details:''' XEP-0045 chatroom at open_chat@conference.igniterealtime.org
 +
    
=== XMPP MUC support for ircd-seven ===
 
=== XMPP MUC support for ircd-seven ===
Line 268: Line 270:  
** http://www.openhab.org/community.html
 
** http://www.openhab.org/community.html
 
** http://mail.jabber.org/mailman/listinfo/iot
 
** http://mail.jabber.org/mailman/listinfo/iot
 +
 +
 +
=== Openfire Session Resumption support ===
 +
* '''Software Project:''' Openfire
 +
* '''Software URL:''' https://igniterealtime.org/projects/openfire/index.jsp
 +
* '''Software VCS URL:''' https://github.com/igniterealtime/Openfire
 +
* '''Software Description:''' Openfire is an XMPP server. It is configured through a web-based admin interface and used in enterprise, military, and government environments.
 +
* '''Brief explanation:''' Openfire currently lacks the session management protocol described in XEP-0198. This provides acking of stanzas across the session, and also the ability to reconnect a session that has been disconnected by network failure. There is no existing infrastructure for such a capability, and the approach needs to consider that Openfire has clustering support; a session may reconnect to a different node within the cluster.
 +
* '''Expected results:''' Each deliverable should be presented as a pull request on GitHub, ready for merge, with tests where appropriate:
 +
** First, simple acking-only should be implemented, with no resumption. This should handle the case where a session is lost, redirecting unacknowledged stanzas to offline storage or other sessions as appropriate.
 +
** Next, resumption should be implemented. There are a number of strategies for this, and it is not entirely clear which strategy will be most successful.
 +
* '''Knowledge Prerequisite:''' Reasonable knowledge of Git, Java and XMPP. Communicating with the team and the XSF Standards SIG will be essential.
 +
* '''Difficulty:''' Hard
 +
* '''Implementation Language:''' Java
 +
* '''Mentor:''' Dave Cridland <dave@cridland.net>
 +
* '''Contact Details:''' XEP-0045 chatroom at open_chat@conference.igniterealtime.org
36

edits

Navigation menu