[ViewVC] Annotation of: cvs/cvsroot/Net-XMPP2/TODO

Net::XMPP2 missing functionality to be RFC 3920 conform:
   - improve error handling for SASL to 
     support retries as specified in RFC 3920.
     (eg. by supporting a method sasl_retry() which takes
      the changed credentials)
   - SRV record lookup: weight handling!
   - test Net::XMPP2::Error for bind_error and stream_error.
   later:
      - make dns resolution async!
      - make extensions more optional and reentrant

Net::XMPP2::IM missing functionality to be RFC 3921 conform:
   - message and presence sending (mostly done?)
   - message and presence receiving
   - 7.2.  Business Rules
   - complete roster stuff
   - handle subscriptions

objectvies to look out for:
   - add high-level events together with low-level events which just
     pass on the XML nodes.
   - TLS: implemented, just do some extensive testing WRT blocking,
          i don't trust the current way the watchers are handled,
          i'm in fear of deadlocks...
Revision:	1.11
Committed:	Sat Apr 21 13:51:39 2007 UTC (19 years, 6 months ago) by elmex
Branch:	MAIN
Changes since 1.10:	+4 -1 lines
Log Message:	implemented the (hopefully) last bits of important error reporting. Net::XMPP was released at the beginngin of this month - damn, i was too slow. But i've taken a look at their code. 17000 lines of code vs. my ~4500 LoC. Also their Java-API is really a mess...
#	User	Rev	Content
1	elmex	1.2	Net::XMPP2 missing functionality to be RFC 3920 conform:
2	elmex	1.11	- improve error handling for SASL to
3			support retries as specified in RFC 3920.
4			(eg. by supporting a method sasl_retry() which takes
5			the changed credentials)
6	elmex	1.2	- SRV record lookup: weight handling!
7	elmex	1.10	- test Net::XMPP2::Error for bind_error and stream_error.
8	elmex	1.7	later:
9			- make dns resolution async!
10			- make extensions more optional and reentrant
11
12			Net::XMPP2::IM missing functionality to be RFC 3921 conform:
13			- message and presence sending (mostly done?)
14			- message and presence receiving
15			- 7.2. Business Rules
16			- complete roster stuff
17	elmex	1.8	- handle subscriptions
18	elmex	1.6
19	elmex	1.7	objectvies to look out for:
20	elmex	1.6	- add high-level events together with low-level events which just
21			pass on the XML nodes.
22	elmex	1.7	- TLS: implemented, just do some extensive testing WRT blocking,
23			i don't trust the current way the watchers are handled,
24			i'm in fear of deadlocks...