Discussion:
xmpp4r examples use of Client.process method
John M Lauck
2009-01-14 23:04:27 UTC
Permalink
Can anyone explain the use of Client.process in most of the example scripts
for xmpp4r?
This method does not appear to be available in the current release and in
all my searches I haven't found any mention of what it was deprecated for
and what new API should be used to handle the same scenario.

A good example is the
xmpp4r-0.4/data/doc/xmpp4r/examples/advanced/getonline.rb script at line 54.


Thanks,

John
Stephan Maka
2009-01-15 13:44:13 UTC
Permalink
Post by John M Lauck
Can anyone explain the use of Client.process in most of the example scripts
for xmpp4r?
This method does not appear to be available in the current release and in
all my searches I haven't found any mention of what it was deprecated for
and what new API should be used to handle the same scenario.
That was the call to the Client to do its work in non-threaded mode. We
largely went for the threaded flavour and many helpers were written that
way.

I guess there are many people out there who prefer mechanisms like
EventMachine over Ruby's abysmal threading performance. Feel free to
send patches (or fork on GitHub).
John Lauck
2009-01-15 14:58:07 UTC
Permalink
Stephan,

Thanks for the info, but I don't prefer one way over another. It's just
hard to learn how to use the xmpp4r lib without a working example.

If anyone could simply explain the new way of handling or working with the
example I mentioned I would have a better grasp on how the xmpp4r lib should
be used.

Also, if there is documentation I'm not aware of that addresses this issue
please point me in that direction.

John
Post by John M Lauck
Post by John M Lauck
Can anyone explain the use of Client.process in most of the example
scripts
Post by John M Lauck
for xmpp4r?
This method does not appear to be available in the current release and in
all my searches I haven't found any mention of what it was deprecated for
and what new API should be used to handle the same scenario.
That was the call to the Client to do its work in non-threaded mode. We
largely went for the threaded flavour and many helpers were written that
way.
I guess there are many people out there who prefer mechanisms like
EventMachine over Ruby's abysmal threading performance. Feel free to
send patches (or fork on GitHub).
_______________________________________________
Xmpp4r-devel mailing list
https://mail.gna.org/listinfo/xmpp4r-devel
Loading...