Difference between revisions of "Interop"

From XMPP WIKI
Jump to navigation Jump to search
 
Line 53: Line 53:
== 2010 Client Interop Participation ==
== 2010 Client Interop Participation ==


Each client instance listed has a ( local-part / password ) pair that should be configured on each server supporting C2S above.
Each client instance listed has a ( local-part / password ) pair that should be configured on each server supporting C2S above. Except for mlinkrelease, because Kev doesn't want the possibility of using his server for spamming. Client devs, please ask Kev directly for mlinkrelease passwords.


* [http://www.boldonjames.com BoldonJames]
* [http://www.boldonjames.com BoldonJames]

Revision as of 13:46, 6 December 2010

XMPP Interop

Plan: to make this the main page for all Interop information, a work-in-progress

2010 Interop

From Monday 6th December through to Saturday 11th December, the XSF will be conducting an online interop event to test and demonstrate XMPP interoperability based on the latest core standards. Client and Server implementers are encouraged to participate.

There is a XEP-0045 chatroom hosted at interop@muc.xmpp.org - if anyone has interop problems connecting to it, this is known to be reachable from jabber.org accounts.

There is also a mailing list interop@xmpp.org - joining it can be done by sending email to interop-request@xmpp.org with a subject line of "subscribe", or alternately by using the Web Interface.

2010 Server Interop Participation

Each participating server has one IM domain, and a chatroom subdomain.

  • Isode
    • Contacts
    • Servers
      • mlinkrelease.xmpptest.com: R14.6 M-Link
      • mlinktrunk.xmpptest.com: R15.0 M-Link (trunk)
        • IPv4 and IPv6 dual-stack
  • Prosody
    • Contacts
    • Servers
      • Prosody 0.8.0, dev.prosody.im ports 5322 (c2s), 5369 (s2s)
  • ejabberd
    • Contacts
    • Servers
      • ejabberd21.xmpptest.com: ejabberd 2.1.x; dev2.process-one.net ; ports 5222 (c2s) 5269 (s2s) 5280 (BOSH); IBR with CAPTCHA
      • ejabberd master; just planned
  • psyced
    • Contacts
    • Servers
      • psyced - s2s only with XEP-0288 and D-W-D support in several configurations (xep-0178-enabled, standard dialback, dwd, bidi)
  • Tigase
    • Contacts
    • Servers
      • tigasetrunk.xmpptest.com: Tigase (trunk)

2010 Client Interop Participation

Each client instance listed has a ( local-part / password ) pair that should be configured on each server supporting C2S above. Except for mlinkrelease, because Kev doesn't want the possibility of using his server for spamming. Client devs, please ask Kev directly for mlinkrelease passwords.

  • BoldonJames
    • Contacts
    • Clients
      • SAFEchat V2.3 ( safechat / safechat )
  • Gajim
    • Contacts
      • Yann Leboulanger XMPP
    • Clients
      • Gajim ( gajim / gajim )
  • Collabora
    • Contacts
      • Sjoerd Simons XMPP
      • Will Thompson XMPP
      • (Emilio Pozuelo Monfort XMPP — not actively working on the XMPP backend, but is writing a search UI which should be able to drive the XEP-0055 code in Gabble)
    • Clients
    • Particularly interested in testing (based on a quick show of hands on the developer channel):
      • XEP-0055
      • XEP-0186 Invisible Command (deferred! how upsetting)
      • Non-Google implementations of google:queue
      • SOCKS5 bytestream proxies
      • Server PEP behaviour when we turn +notify on and off on the fly. Specifically: do updates that occur while we do not have +notify set get pushed to us when we turn it back on?
  • OneTeam
    • Contacts
    • Clients
      • OneTeam ( oneteam / oneteam )