Comments on: IM Integration with XMPP4r - 2 mistakes to avoid http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/ Because programming should be fun Fri, 12 Mar 2010 13:31:48 +0000 http://wordpress.org/?v=2.1.2 By: IceskYsl http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-539 IceskYsl Wed, 13 Feb 2008 09:15:20 +0000 http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-539 I use backgroundrb in rails to do this ~ I use backgroundrb in rails to do this ~

]]> By: John Yerhot http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-541 John Yerhot Thu, 14 Feb 2008 03:00:30 +0000 http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-541 "I use backgrounrb in rails to do this ~" Me too - I have a BackgrounDrb worker that is called every 60 minutes that uses Xmpp4r to send an IM and it works very nicely. Like you were talking about, it also separates out the Rails app from the "listener" (or worker with BackgrounDrb). “I use backgrounrb in rails to do this ~”
Me too - I have a BackgrounDrb worker that is called every 60 minutes that uses Xmpp4r to send an IM and it works very nicely. Like you were talking about, it also separates out the Rails app from the “listener” (or worker with BackgrounDrb).

]]> By: Matt Garland http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-697 Matt Garland Sat, 27 Sep 2008 03:39:26 +0000 http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-697 Frank! I had whiteboarded this structure to code tomorrow when I googled around and found your warning. Now, what if EVERYTHING I wanted my Rails app to do was unilateral? Users creates account, and rails creates a jabber account for them, too. User changes friend preferences in Rails, and Rails updates roster of friend. Account is deleted, and Rails tells the server to stop saving the equivalent JID. Would that still smell? The rails and jabber will even be on the same machine. Do I really need confirmations, even? Anyway, thanks for the head up. matt Frank! I had whiteboarded this structure to code tomorrow when I googled around and found your warning.

Now, what if EVERYTHING I wanted my Rails app to do was unilateral? Users creates account, and rails creates a jabber account for them, too. User changes friend preferences in Rails, and Rails updates roster of friend. Account is deleted, and Rails tells the server to stop saving the equivalent JID.

Would that still smell? The rails and jabber will even be on the same machine. Do I really need confirmations, even?

Anyway, thanks for the head up.

matt

]]> By: Matt Garland http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-698 Matt Garland Sat, 27 Sep 2008 04:04:21 +0000 http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-698 More googling brought your point home, Frank. Here's a Railsforum post that step by step shows you how to create this backgroundrb listener: http://railsforum.com/viewtopic.php?id=1033/ More googling brought your point home, Frank. Here’s a Railsforum post that step by step shows you how to create this backgroundrb listener: http://railsforum.com/viewtopic.php?id=1033/

]]> By: Frank http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-701 Frank Fri, 03 Oct 2008 21:08:39 +0000 http://www.rubyfleebie.com/im-integration-with-xmpp4r-2-mistakes-to-avoid/#comment-701 Matt, I can't be of any help with backgroundrb since I had a lot of problems configuring it... so much that I gave up and made a separate listener instead. For some reasons Backgroundrb slowed down our application a lot and made it very unstable. Since our listener doesn't contain any business logic, the fact that I don't have access to the Rails application data isn't a problem at all. What I also like with this setup is the fact that it forces you to see the listener as a separated project. It can have its own repository, its own capistrano deployment recipes... so when you find a bug in the listener, you only have to commit/deploy the listener project while the rails application remains untouched. EDIT: Oh and I forgot to answer your your first comment, sorry. Sure, if you don't need to establish a bi-directional conversation with your users, you do not need a "listener". However your rails app would still have to create a jabber connection (with the whole authentication process) at every requests which would be far from ideal. The best is still to stick with a separated listener (custom or backgroundrb). Thanks for your comment! Matt,

I can’t be of any help with backgroundrb since I had a lot of problems configuring it… so much that I gave up and made a separate listener instead. For some reasons Backgroundrb slowed down our application a lot and made it very unstable. Since our listener doesn’t contain any business logic, the fact that I don’t have access to the Rails application data isn’t a problem at all. What I also like with this setup is the fact that it forces you to see the listener as a separated project. It can have its own repository, its own capistrano deployment recipes… so when you find a bug in the listener, you only have to commit/deploy the listener project while the rails application remains untouched.

EDIT: Oh and I forgot to answer your your first comment, sorry. Sure, if you don’t need to establish a bi-directional conversation with your users, you do not need a “listener”. However your rails app would still have to create a jabber connection (with the whole authentication process) at every requests which would be far from ideal. The best is still to stick with a separated listener (custom or backgroundrb).

Thanks for your comment!

]]>