Re: [lopsa-tech] Anybody wanna chat? - Internal chat server advice

2011-06-01 Thread Nick Whalen
Seconded. I run Openfire at work to allow several offices to communicate with each other and I've never had a problem with it. It doesn't take much in the area of resources to run (despite being Java), and setup is a breeze. There's also a good quantity of plugins available for it, which

Re: [lopsa-tech] Anybody wanna chat? - Internal chat server advice

2011-06-01 Thread Chris McEniry
We have a new requirement of sorts for a chat server that supports private persistent rooms with some sort of logging/archive feature. I have started looking at mu-conference to add to our jabber2 server but not sure if it meets all our requirements. I'm running ejabberd. It supports all

Re: [lopsa-tech] Anybody wanna chat? - Internal chat server advice

2011-06-01 Thread Paul Heinlein
On Wed, 1 Jun 2011, Chris McEniry wrote: I'm running ejabberd. It supports all of the items you listed. It's not as straight forward to configure as openfire, but it works well for us. (It's not Java so pick your poison.) ejabberd has been stable for us, too, but it requires an Erlang

Re: [lopsa-tech] Anybody wanna chat? - Internal chat server advice

2011-06-01 Thread Gary Pitman
Thanks everyone, I have the openfire product up authenticating against our openldap and seems pretty nice. One thing that I have found is that pidgin seems to be unable to perform the password dialog for password protected rooms. Is this my error or has anyone else found this? (empathy and

Re: [lopsa-tech] Anybody wanna chat? - Internal chat server advice

2011-06-01 Thread Yves Dorfsman
On 11-06-01 04:40 AM, Adam Tauno Williams wrote: +1 OpenFire; it really is painless, simple to setup, feature-complete, and reliable. Other than being Java container application [Blech!] which makes setting up SSL/TLS a pain there really aren't any downsides. Yes, adding the certificate is

Re: [lopsa-tech] Anybody wanna chat? - Internal chat server advice

2011-06-01 Thread jeff
On 06/01/2011 07:03 PM, Nathan Hruby wrote: Also, I have found the latest version not as stable as the previous one. It looks like there's a memory leak in it somewhere. I have solved this by cron'ing a re-start in the early morning when it is the less likely that anybody's chatting. We hit