comment on

Hello,

POE::Component::Jabber works pretty well for my needs (persistent daemon that deals with presence and passing messages between the mobile network and email system) and is definetly worth a look if you like POE. You may also check out Net::XMPP2, which you mentioned in your original post. It seems that Net::XMPP2 will be renamed to AnyEvent::XMPP later, but for now they're the same thing.

Good luck.

P.S. I'm afraid that you'll have to go back to the RFC in order to see how to deal with presence, subcriptions, roster etc. These mechanisms are in the core of XMPP/Jabber and should be understood by anyone who wants to deal with this protocol.

In reply to Re: What's the current way to program Jabber? by kirillm
in thread What's the current way to program Jabber? by titivillus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks