In the process of troubleshooting issues with dying connections I made the change for configurable KeepAlives. When that still didn't solve the problem, I added a new channel for unhandled events as well as changing the way keep alives are done to use the documented mechanism for pings here:

https://ecosystem.atlassian.net/wiki/display/HCDEV/HipChat+XMPP+Protocol+Documentation#HipChatXMPPProtocolDocumentation-Pings (the XEP-0198 implementation)

Instead of creating a specific channel for acks, I just used the new channel so my upstream application could handle them.

It seems that the XMPP interface at port 5222/5223 will be closed with newer HipChat server versions. Is der any idea how to support this change?

https://confluence.atlassian.com/hc/hipchat-server-release-notes-608731400.html

Quick PR to fix #20

There are probably more elegant ways to fix this, like having a more generic 'xmppDomain' parameter to NewClientWithServerInfo() with a default of 'hipchat.com' and then defining clientDomain like

"chat." + xmppDomain

and mucDomain like

"conf." + xmppDomain

Let me know what you think.

Upon joining a room, HipChat sends a dump of the room's recent history, which I want to filter out. This library does not expose any timestamp data (which I assume hipchat provides for these history messages). And I can't seem to connect as a bot by joining rooms with a JID of "bot" as per this support page.

Hi, i'm trying to use your library to connect to a self hosted hipchat instance and facing a problem with the TLS connection. I'm everytime getting the following error: client error: x509: certificate has expired or is not yet valid So it seems that the certificate is expired but I want to connect anyway. So how can I disable the Cert verify? Thanks

Private messages are 1-1 messages between two parties, using an XMPP type of 'chat'. In order to retain full backwards compatibility, this commit adds the new function 'PrivSay' rather than changing the 'Say' function to require an additional flag.

This problem can be reproduced by connecting to hipchat and changing the name of a user.

The receivedRooms and receivedUsers channels are unbuffered, so sending data to this channel will block until something receives from this channel. The only time these channels are received from are in the Users() and Rooms() methods.

However, these messages generate a request so would still leave the listen thread blocked. We exposed the channels and used a goroutine similar to this to avoid the endless block. Note: Rooms() and Users() in this example just return the channels and don't make requests (the same as Messages()).

go func() {
    for {
        select {
        case message := <-client.Messages():
            log.Printf("Received message: %v", message)
        case rooms := <-client.Rooms():
            log.Printf("Received rooms: %v", rooms)
        case users := <-client.Users():
            log.Printf("Received users: %v", users)
        }
    }
}()

Obviously there still needs to be work done to communicate received rooms and users to other goroutines, but this is one way to avoid the problem.

While in the reply example you are listening to the incoming messages and someone changes his nickname via the web interface the connection will time out and the bot will shortly disconnect.

It only happens in this scenario.

Passwords containing Predefined XML entities should be escaped when used during auth.

Before

<iq type='set' id='1234567890'><query xmlns='jabber:iq:auth'><username>12345_67890</username><password>Foob&R</password><resource>bot</resource></query></iq>
client error: read: connection reset by peer

After

<iq type='set' id='1234567890'><query xmlns='jabber:iq:auth'><username>12345_67890</username><password>Foob&amp;R</password><resource>bot</resource></query></iq>

This is a PR to fix the issue discussed in #8. We've been using the code with these changes for a couple weeks now and none of our bots are hanging like they used to.

I also updated the examples to be use the channels instead, as @fedyakin shows in the above issue, a normal structure would probably look something like this:

go func() {
    for {
        select {
        case message := <-client.Messages():
            log.Printf("Received message: %v", message)
        case rooms := <-client.Rooms():
            log.Printf("Received rooms: %v", rooms)
        case users := <-client.Users():
            log.Printf("Received users: %v", users)
        }
    }
}()

Let me know if you have any question.

This adds the ability to receive and send private messages.

Received private messages are added onto the Messages channel, so the user implementing it will need to parse the message.From themselves to check whether it was from a room or from a user.

When sending a message, it will check if the to address contains the text @chat.hipchat.com. This means that we're sending it to a user instead of a room (which would be @conf.hipchat.com), and changes the message type of the xml accordingly.

Hello,

Duration of KeepAlive() is hard-coded so we cannot change that. Accordingly, I added a new function KeepAliveBy(sec time.Duration) to configure duration.

Related: #12