Besides client and server, there is a Connection Manager entity in BOSH architecture. Client communicates with CM via HTTP POST requests/responses defined in mentioned XEPs and CM communicates with XMPP server either acting as a ordinary XMPP client or using component protocol. CM can be standalone HTTP server or built-in functionality (or extension) of XMPP server. If you want to connect to XMPP server via BOSH CM, you need CM URL and CM port number (e.g. "http://bind.jabbim.cz/" and 80 for jabbim.cz[in czech]) in addition to XMPP server address and port. With built-in Connection Managers, IP addresses of XMPP server and CM will be the same and just the port numbers will differ.
Follows overview of XMPP software with BOSH support.
Servers with built-in Connection Manager.
- Openfire - XEP-0124 listed in supported XEPs.
- ejabberd - Release notes for version 2.0.0 mention XEP-0124 support. I installed and it offers SASL mechanisms in initial response, so I guess XEP-0206 is supported as well.
- Tigase Server - BOSH support since 3.0.2
Act as a proxy between client and XMMP server.
- Araneo - Minimal CM written in Python using Twisted. I found the link on MattJ's blog
- Punjab - Python and Twisted again.
- rhb - CM in Ruby.
- JabberHTTPBind - Java servlet implementing XEP-0124.
- gloox (C++) - BOSH support done by MattJ during GSoC 2007. BOSH Connection classes are included in svn trunk and 1.0-beta2 (download page).
- xmpp4r (Ruby)
- emite (Google Web Toolkit, Java) - XMPP library and client GUI for gwt, connecting through BOSH Connection Manager.