| … | |
… | |
| 97 | What the return values do depends on the event now. |
97 | What the return values do depends on the event now. |
| 98 | |
98 | |
| 99 | The highlight of this release is the implementation of XEP-0114, the |
99 | The highlight of this release is the implementation of XEP-0114, the |
| 100 | Jabber Component Protocol. |
100 | Jabber Component Protocol. |
| 101 | |
101 | |
|
|
102 | It's possible to get a DOM tree from a Net::XMPP2::Node now and also |
|
|
103 | to receive the original parsed "XML" from it, which should enable |
|
|
104 | full access to the "XML" data that was received. This also allows |
|
|
105 | easy integration with other XML Perl modules. |
|
|
106 | |
| 102 | You can also set the initial priority of the presence in |
107 | You can also set the initial priority of the presence in |
| 103 | Net::XMPP2::IM::Connection now. |
108 | Net::XMPP2::IM::Connection now. |
| 104 | |
109 | |
| 105 | Please consult the Changes file for greater detail about bugfixes |
110 | Please consult the Changes file for greater detail about bugfixes |
| 106 | and new features. |
111 | and new features. |
| … | |
… | |
| 133 | enhancements along with some todo items killed from the TODO file. |
138 | enhancements along with some todo items killed from the TODO file. |
| 134 | |
139 | |
| 135 | TODO |
140 | TODO |
| 136 | There are still lots of items on the TODO list (see also the TODO file |
141 | There are still lots of items on the TODO list (see also the TODO file |
| 137 | in the distribution of Net::XMPP2). |
142 | in the distribution of Net::XMPP2). |
| 138 | |
|
|
| 139 | Sadly this module still misses some decent DOM implementation. Do you |
|
|
| 140 | know some decent DOM Level 2 implementation for Perl? (I considered |
|
|
| 141 | switchting to XML::LibXML but I somehow have more trust in the "expat" |
|
|
| 142 | XML parser, maybe someone wants to implement XML::LibXML based parsing |
|
|
| 143 | for me (and of course a DOM interface for Net::XMPP2::Node?) |
|
|
| 144 | |
143 | |
| 145 | Why (yet) another XMPP module? |
144 | Why (yet) another XMPP module? |
| 146 | The main outstanding feature of this module in comparison to the other |
145 | The main outstanding feature of this module in comparison to the other |
| 147 | XMPP (aka Jabber) modules out there is the support for AnyEvent. |
146 | XMPP (aka Jabber) modules out there is the support for AnyEvent. |
| 148 | AnyEvent permits you to use this module together with other I/O event |
147 | AnyEvent permits you to use this module together with other I/O event |
| … | |
… | |
| 246 | Please note that I'm currently (July 2007) the only developer on this |
245 | Please note that I'm currently (July 2007) the only developer on this |
| 247 | project and I'm very busy with my studies in Computer Science in Summer |
246 | project and I'm very busy with my studies in Computer Science in Summer |
| 248 | 2007. If you want to ease my workload or want timely releases, please |
247 | 2007. If you want to ease my workload or want timely releases, please |
| 249 | send me patches instead of bug reports or feature requests. I won't |
248 | send me patches instead of bug reports or feature requests. I won't |
| 250 | forget the reports or requests if you can't or didn't send patches, but |
249 | forget the reports or requests if you can't or didn't send patches, but |
| 251 | it can take a long time until I get enough time to fix/implement them. |
250 | I can't gurantee immediate response. But I will of course try to |
|
|
251 | fix/implement them as soon as possible! |
| 252 | |
252 | |
| 253 | Also try to be as precise as possible with bug reports, if you can't |
253 | Also try to be as precise as possible with bug reports, if you can't |
| 254 | send a patch, it would be best if you find out which code doesn't work |
254 | send a patch, it would be best if you find out which code doesn't work |
| 255 | and tell me why. |
255 | and tell me why. |
| 256 | |
256 | |
