building a wave server

Printer-friendly version

As I explore the FedOne and other bits and pieces I thought I would put together some notes on what would be required to build a hypothetical wave server.

Components:

XMPP Server:

The federation protocol is XMPP based and the various proposed Canonical Client Server Protocols are all based very firmly in XMPP. Thus any new Wave server will need to either piggy back on existing XMPP infrastructure or hand the XMPP stuff within itself.

Email:

If Wave is to ever "replace email" it needs to be able to talk to email. This means that the integration between Wave and Email needs to happen below the level of Extensions. Any new Wave server will need to be able to speak SMTP. This will of course necesitate the installation and management of anti-virus and anti-malware software.

Wave Server:

Client Port:

At some point there is going to be a Standard agreed upon for the communication between clients and servers. Your Wave server is going to need to be able to support this standard.

Agent API:

This is another area where there is going to need to be standardisation. This will both make developing Agents and other Extensions easier as well as encouraging the development of an Agents Marketplace.

Persistance:

Yup, you're going to need to be able to store your waves so that they survive beyond the next reboot. I'd suggest starting with one of the more decent DB's out there such as MySQL or Postgres.