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.

Ruby Fleebie » IM Integration With XMPP4r : Part 2…

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

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

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?

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

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.

Note : Script#2 and Script#3 is in the same host

This way, I can use XMPP for 2-way comunication between any application or any embeded device, regardless of excessive bandwidth usage caused by xml overhead.

However, there are some little mistakes that i wanted to point out here.
Well I pasted the codes right from the web site and here was the persisting error that kept coming at me when trying to execute the script:

Jabber_test_ruby.rb:81: syntax error, unexpected ‘}’, expecting kEND
Jabber_test_ruby.rb:92: syntax error, unexpected $end, expecting kEND
Tk.mainloop
^
it’s just because you forget to write the “end”s closing block of the callback methods(not all of them).

Anyway keep up the good work, I’ll come back here.

I’m sure you have your answer already, but let me explain the “running in their own thread” thing :

The callbacks are invoked in the context of the “parser thread” which is the one doing the actual “listening” of the the XML stream. When something happens in the parser thread (e.g. message stanza received), callbacks are invoked from there. So the code you have in your various callbacks are effectively executed in another thread context.

Like Leonardo wrote, you have to write Thread.stop in your main thread when you have set all your callbacks and other initialization stuff.

It might sound confusing, but you have to write Thread.stop to keep the current thread alive. Thread.stop simply put the current thread into sleep mode and leave all the scheduling time to the other threads (the parser thread in our case). If you don’t write Thread.stop, everything ends when the main thread has nothing left to do.

I have updated the original post.