Jabber does have a different philosophy. The clients can just do the Jabber protocol. It is the server, that adds the capability to talk to other networks and it does that in quite some generic way. So basically this makes it much easier to provide a client implementation.
Still it might be, that if you want to talk to people on the M$ network, that it is not the best solution for that. But for the original case, to connect developers working in different locations, it seems great to me and am using it every day just to do so.
As it is so easy to use and extend jabber we have lots of bots around that help us automate our tasks, e.g. we have a bot telling us when the build failed or succeeded. We're just talking about a handful of lines of code.
Tough, there is an option with HTTP-polling and jabber across an HTTP-proxy though, but I never tried that.
Anyway, the VPN shouldn't be to slow. That data exchanged is not hughe and the frequency of message is also low. Furthermore using the VPN the connections wouldn't need to be re-established for every message, so I would guess that connection speed doesn't matter.
If you want a closed group like for team communication, why don't you go for jabber? You could setup your own server in seconds (at least with debian: apt-get install jabber), have your own rooms and don't have to bother too much about the internet and firewalls.
It is truly open source. That includes the protocol, most client-apis, most clients and most servers. Furthermore the core is already in IETF RFCs.
No need to worry about vendors checking the protocols anymore and a wide variety of clients to use.
Watch out, your favorite IDE might even get a plug-in for IMing.
Slashdot Mirror
I understand your concerns.
Jabber does have a different philosophy. The clients can just do the Jabber protocol. It is the server, that adds the capability to talk to other networks and it does that in quite some generic way.
So basically this makes it much easier to provide a client implementation.
Still it might be, that if you want to talk to people on the M$ network, that it is not the best solution for that. But for the original case, to connect developers working in different locations, it seems great to me and am using it every day just to do so.
As it is so easy to use and extend jabber we have lots of bots around that help us automate our tasks, e.g. we have a bot telling us when the build failed or succeeded. We're just talking about a handful of lines of code.
Tough, there is an option with HTTP-polling and jabber across an HTTP-proxy though, but I never tried that.
Anyway, the VPN shouldn't be to slow. That data exchanged is not hughe and the frequency of message is also low. Furthermore using the VPN the connections wouldn't need to be re-established for every message, so I would guess that connection speed doesn't matter.
If you want a closed group like for team communication, why don't you go for jabber? You could setup your own server in seconds (at least with debian: apt-get install jabber), have your own rooms and don't have to bother too much about the internet and firewalls.
It is truly open source. That includes the protocol, most client-apis, most clients and most servers.
Furthermore the core is already in IETF RFCs.
No need to worry about vendors checking the protocols anymore and a wide variety of clients to use.
Watch out, your favorite IDE might even get a plug-in for IMing.