2 use qca syncthread, match keystore in thread safety concerns
3 "Interface ids obtained through NetInterfaceManager are guaranteed to be valid until the event loop resumes, or until the next call to interfaces() or interfaceForAddress()." ... the code seems to be lying about interfaceForAddress.
6 support faking srv (or perhaps any record) somehow, through config or code
8 put the netnames backend into an alternate thread (this thread should
9 probably be some generic irisnet thing that other modules can use too)
10 netnames front-end api communicates with the backend, so that one backend
11 is shared by all threads
12 NameResolver/ServiceBrowser/ServiceResolver should have isActive?
13 report ServiceBrowser error codes
14 report ServiceResolver error codes
15 ServiceInstance attribs arg of constructor should be optional?
16 ServiceInstance should cache the name() answer
17 ServiceProvider should support error codes and passing many ip addresses
18 ServiceResolver should give the hostnames and the ip addresses. hostnames
19 may be needed for SASL
20 consider reverse dns (for both internet and multicast)
22 dns/bonjour/idn/dns-sd
23 tcp/udp/rtp, bytestream abstraction
24 protocol http/socks/ice/ocsp/crl
25 lineproto, httpproto, xmlproto, binaryproto?, socksishproto?
26 auth/cert/pgp parameter abstraction
27 network interface detection
28 simplified keystore handling?
30 built-in simplified SASL digest-md5, plain?, anonymous?
31 layer tracking & flow control
32 both sync and async api
34 proxies http/httpsconnect/httppoll/socks4,5/fakessl?
35 dns/net/proxy/auth engine plugins?
36 upnp/bonjour nat dodging / port opening?
41 2) how would a pgp-auth for xmpp-core work?
44 support xmpp-core for tcp/httpbind
45 xmpp-core should be "just another protocol"