Comments on: IM Integration With XMPP4r : Part 2

By: Dan Simard

Dan Simard — Tue, 29 Jan 2008 14:18:56 +0000

It was completly clear! I’m glad you write about XMPP4R because nobody wants to talk about it… almost no documentation, no examples and no blog posts. Is XMPP4R taboo?

By: links for 2008-01-30 « Bloggitation

links for 2008-01-30 « Bloggitation — Wed, 30 Jan 2008 00:21:17 +0000

[…] IM Integration With XMPP4r : Part 2 (tags: ruby jabber programming) […]

By: IceskYsl

IceskYsl — Wed, 30 Jan 2008 01:43:13 +0000

so cool~ thx~

By: Stephane Wirtel

Stephane Wirtel — Wed, 30 Jan 2008 09:02:41 +0000

I don’t know if XMPP4R is taboo, but I am interrested by this project. A bit of documentation would be welcome.

By: IceskYsl

IceskYsl — Wed, 30 Jan 2008 10:03:28 +0000

A chinese version is here..
http://docs.google.com/View?docid=dhf86kr9_188gmpnw5hf

By: Tyler

Tyler — Wed, 30 Jan 2008 19:33:52 +0000

Hey, thanks a lot. I’ve coincidentally been playing around with this a bunch. I’ve been having a problem with status synchronization with Google Talk. For example, say I want to connect, get my status, message it to a test account, then update it. I can’t seem to get the changes to apply if I login to Google Talk from another client (say GMail) Any ideas?

By: Frank

Frank — Thu, 31 Jan 2008 13:12:49 +0000

@Dan,

Yeah sometimes I wonder if Xmpp4r is taboo too… no one wants to talk about it! I have to say it is not the most actively supported gem around. I’m currently seriously thinking about writing my own for XMPP. Next step is to stop thinking about it and to actually do it

@Tyler,

Are you talking about the status itself (busy, available, etc) or the status message? We have experienced problems trying to set the status message with XMPP4r and we have simply stopped investigating on the issue.

If you are speaking about the status itself that doesn’t update… well I’m not quite sure about the source of the problem. Maybe it has something to do with the fact that you are trying to set your status manually (technically it should work but there might be a bug in xmpp4r). Could you send me the code you are using to accomplish what you want? I would be more able to help you with your problem.

By: roScripts - Webmaster resources and websites

roScripts - Webmaster resources and websites — Thu, 31 Jan 2008 16:15:06 +0000

Ruby Fleebie » IM Integration With XMPP4r : Part 2…

Ruby Fleebie » IM Integration With XMPP4r : Part 2…

By: Mislav

Mislav — Mon, 04 Feb 2008 05:32:25 +0000

Frank,

It’s great that you’re writing about this. Both were excellent articles and I hope you’ll keep it up.

By: Frank

Frank — Mon, 04 Feb 2008 16:21:25 +0000

@Mislav,

I’m glad you like the articles. There will be a 3rd part for sure (that might be the final one, but I’m not sure of yet).

I really think IM integration is not used enough in today web applications. Some people see it as a gimmick, but to me nothing could be farther from the truth.

Thanks for your comment

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

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

[…] 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 to continue the series on his […]

By: Don Park

Don Park — Sat, 22 Mar 2008 16:39:42 +0000

mangled resource names?
i connect with
jid = JID::new(’me@gmail.com/yin’)
client = Client::new(jid)
client.connect(’talk.google.com’)
client.auth(password)
it took a while to figure out how to connect to talk.google.com instead of gmail.com

and send with
to = “me@gmail.com/yang”
subject = “from yin to yang”
body = “help”
m = Message::new(to, body).set_type(:normal).set_id(’1′).set_subject(subject)
puts “sending: #{m.inspect}”
client.send m

i have a ‘yang’ version of the same program to receive the message. yang never gets the message and my pidgin IM program pops up with the “help” message from
me@gmail.com/yin04223891

do you know whats with the extra digits in the resource name?

By: Nilu

Nilu — Thu, 10 Apr 2008 11:09:58 +0000

I was trying to implement a chat client using this tutorial but it seems that my messages do not get recieved. I am using a local host for this. The client seems to send the messages (at least it doesn’t give me any errors) but when i run an another instance of the program and try to recieve messages, the messages do not show. Any ideas as to why this may be? Thank you in advance for any help

By: Frank

Frank — Thu, 10 Apr 2008 11:56:11 +0000

@Don Park,

Sorry for the late answer. The digits after the resource name is an auto-generated ID… you do not have control over it. I believe it gets assigned by your Jabber server (in this case, talk.google.com).

Now about the problem you are facing, I realize I forgot to include something important in my article..shame on me. You have to subscribe to the other contact. I update the original post, look above.

@Nilu,

It is probably my fault for that again! I forgot to talk about the subscription part.. look at the end of this post… I wrote an update. I’m sorry about that

By: Nilu

Nilu — Thu, 10 Apr 2008 23:06:26 +0000

Thanks for the update!

By: Nilu

Nilu — Thu, 10 Apr 2008 23:22:56 +0000

I also found out that Client class does not contain ‘add_update_callback’ the Rsoter::Helper class does…

By: Nilu

Nilu — Thu, 08 May 2008 10:28:34 +0000

You said that the callbacks are in a separate thread, so then how will the main thread (which is the client) actually receive the message? How would it communicate with the client? I don’t seem to be able to receive messages, although i can send them successfully even when i use the roster.

By: Leonardo Boiko

Leonardo Boiko — Wed, 25 Jun 2008 02:08:53 +0000

@Nilu: I had the same problem as you. Looking at the examples that came with the debian package libxmpp4r-ruby-doc, I found this:

Thread.stop
client.close

next to the end of the script, after you set your callbacks. Works for me. See echo_threaded.rb for more.