Jabber is an "architecture", and therefore consists of many different components and projects. The 1.0 release is only for the core server, which involves libjabber, jserver, and etherx. The numerous other projects and teams will likely reach a 1.0 status around the same time, but this document is not making any statements about those efforts.
(a + means the assigned person is looking for help with the task)
|Overhaul the autoconf/automake build system, better tests/xp checks
|XP issues with dlopen and family, use libtdl and allow for static builds
|Improve the logging data for etherxd and jserver, document and have sample log formatters/stats.
|Complete API overhaul.
|Three API types: svc[Services], mod[Modules], and xdb[XML Data storage].
|Look at using hashes and adjusting other data models internally
|user data references tracked and freed when not used. Hash for main user and resource lookup.
|Implementing a protocol-level keepalive function to check for broken sockets
|plan is to send whitespace at timed intervals between the main elements
|better error checks/handling, testing for validity of data, etc
|Allow for different types of resources, hidden, shadow, etc
|Server will no have this built in, but modules can implement this using agents.
|Use gettext for error messages and other strings.
|Protect the secret from the wire
|Use hashes (MD5)
|And Family (any data stream), negotiating location, starting, etc. SOCKS?
|jer, temas, +
|Full doc being written, but get started by looking at the jabber:x:oob namespace.
|Between any entity, clients, servers, transports, etc. NOT for negotiating aspects of a feature, just the yes/no existance of it.
|Agent/Transport/Service handling, type: issue (icq:123454), server listing available transports, etc.
|all URI's in jabber are "jabber:" for now, and jabber:iq:agents for listing transports/etc on a server
|Jabber Universal Data: jabster, user searching, master server list, etc.
|temas, jer, +
|Typical Client2Client stuff, ping, traces, version, but could be between any jabber entity
|Maturation of the jabber:iq:register IQ
|Standard user info, setting and fetching.
|Uses the vCard XML IETF proposal.
|How is the presence/messages handled for group chats, or chatrooms, joining, nicks, etc.
|basics implemented (participants level), no administration yet
|XML Stream level redirection.
|Upon connecting, if the stream root greeting has a redirect="184.108.40.206" attribute, the connector should use that IP and attempt to connect again.
|List the exact valid characters for the Jabber ID.
|The username is under the same restrictions as SMTP, the host is normal DNS name restrictions, and the resource has no restrictions.
|Basic ICQ transport
|partially implemented (libicq)
|Basic AIM transport
|partially implemented (libfaim, oscar)
|Basic Yahoo Pager transport
|partially implemented (yahoolib.c)
|Basic MSN transport
|MSN Messenger lib in Java was mentioned?
|Receiving Email immediately in Jabber using a special email address(firstname.lastname@example.org), and replies being delivered via email.
|Simple chatrooms, bundled with jserver
|Talk/Finger/R* services that query a jabber server directly.
|A special transport to assist in file transfers, bridge between two clients via the server, optionally allow offline file xfers.
|Two main types of features needed here: SOCKS type (stream through a 3rd party) and HTTP storage type (offline file exchanges).
|Check any POP box for new messages and send alert.
|Plan to do w/ perl.
|stores user data in simple files
|stores user data in mysql
|uses standard unix data (/etc/passwd)
|auth against a radius DB
|uses a LDAP server for user data
|Allow shared roster groups
|Broadcast messages to everyone (for admins)
|Query server status and change variables on the fly, active user list, etc
|Allow multiple authenticated users/resources via one socket, for proxies or advanced clients.
|Any IRC client can connect directly to jserver and log in as a jabber client
|a simple text-based interface built into jserver, similiar to a moo/mud
|For web based clients, allow HTTP access, for clients behind firewalls/proxies also.
|Shell tools, other lightweight UNIX environment jabber apps
|XUL based client/libs, full Jabber integration with Mozilla
|eric, jer, +
|uses HTTP service