Hi, I kept getting stung by the change with Ruby 1.8.6 and xmpp4r. I had just starting experimenting with xmpp4r-simple and found that in xmpp4r, assumptions were made about unlocking mutexes locked by other threads. This was confirmed here:
https://mail.gna.org/public/xmpp4r-devel/2007-06/msg00012.html So I did partial fix and a partial hack. For stream.rb, connection.rb, client.rb, I replaced the Mutex stuff with a proper condition variable. That's the "fix" bit. ThreadBlock class still caused me trouble. I have not had time to add the condition variables here yet (I really should be doing the work I'm paid to do ;) so I commented out the threading completely from ThreadBlock. This will naturally Cause Errors(tm) at some point. That's the "hack" bit. Anyway, it's halfway there. I can at least connect to gtalk and do some stuff now. Regards, Luke. -- Luke Burton. Yes, questions. Morphology, longevity, incept dates.
xmpp4r.diff
Description: Binary data
_______________________________________________ Xmpp4r-devel mailing list [email protected] https://mail.gna.org/listinfo/xmpp4r-devel
