Comments on: IM Integration With XMPP4r

By: Akita

Akita — Tue, 02 Feb 2010 22:33:26 +0000

Akita…

Ruby Fleebie ” IM Integration With XMPP4r was a very useful post….

By: Frank

Frank — Tue, 14 Jul 2009 15:44:55 +0000

@Kirill,

Thanks for your support! I really want to continue to write on a consistant basis but as of late it has been very difficult to do. And yes, XMPP is the topic that I want to discuss the most. I plan to start writing about our XMPP integration in TimmyOnTime (company project).

Again, thanks for your support. I’ve been a very dead blogger since a while, But there is absolutely zero possibility of pulling the plug on RubyFleebie for the moment.

By: Kirill

Kirill — Tue, 14 Jul 2009 14:20:52 +0000

Will you continue the series of article? I’m new to ruby and XMPP. Very glad that your blog was start for me.

By: vinibaggio » Distributed Ruby (DRb) + XMPP4R

vinibaggio » Distributed Ruby (DRb) + XMPP4R — Sat, 15 Nov 2008 13:56:46 +0000

[...] do tutorial e por isso recomendo algumas leituras prévias sobre XMPP4R (a documentação oficial, este tutorial, e sua segunda parte) e de Rails (recomendo os tutoriais e screencasts do Fábio Akita, no seu [...]

By: Introduction to XMPP and XMPP4R for Ruby Developers | Computer & Internet

Tue, 12 Feb 2008 00:40:24 +0000

[...] a two part tutorial / guide to using XMPP4R to integrate with Instant Messaging systems. The first part is a basic overview, and the second part is a basic demo of creating an XMPP client. Frank expects [...]

By: Introduction to XMPP and XMPP4R for Ruby Developers

Introduction to XMPP and XMPP4R for Ruby Developers — Sun, 03 Feb 2008 20:46:44 +0000

By: IceskYsl

IceskYsl — Thu, 31 Jan 2008 06:59:07 +0000

A chinese version is here.thx~
http://iceskysl.1sters.com/?action=show&id=204

By: » The Links » roarin’ reporter

» The Links » roarin’ reporter — Tue, 04 Dec 2007 03:27:23 +0000

[...] IM Integration With XMPP4r [...]

By: Frank

Frank — Mon, 03 Dec 2007 23:05:09 +0000

@jro,

Thanks for the info… that’s what I thought. So I guess my best bet would be to go with OpenFire? I don’t think that the high memory usage issue is so bad compared to the complexity of the other servers.

@Karl,

For ToT, we are currently using the Google chat servers (we use the “Google for your domain” service). We then asked our hoster to change our SRV records to have them point on Google servers. We are really happy with this setup so far… even if it makes us “depend” of Google (who doesn’t? :) ). However, we might want to setup our own jabber server in the future.

By: Karl

Karl — Mon, 03 Dec 2007 22:33:34 +0000

And the timing couldn’t be better… I just started IM functionality that I promised my customer (foolishly, before I knew I could do it). It appears that the reliability of such a system depends entirely on the Jabber (OpenFilre, Ejabberd, etc.) server. For TOT id you run your own server, or use a public one?