This page describes the ongoing effort to provide a stable API within MediaWiki for convenient access to machine-readable data.
You are going to get hacked…
Joe Stump, Lead Architect, Digg. Slides should make its way at Joe’s website soon enough.
Mainly works on the backend, makes sure its scalable, can all the Digg buttons be served, et al.
Application layer is loosely coupled from your data. Whole point of SOA? You can put a service in front of the DB, and move between DB’s if required.
They do use MySQL, but its pretty vanilla.
MySQL application developers have some problems with connection state. There is a lot of state which can be used associated with a single connection
* Transactions (autocommit, uncommitted work, when a transaction was started, isolation level)
* Temporary tables
* Session variables which affect behaviour
* Other session variablesIf you can avoid all of these, then you can benefit from transparent auto-reconnection and transparent connection reuse / pooling etc.
XMPPHP is the successor to Class.Jabber.PHP that I've been promising for years. Taking advantage of PHP5, I believe it to be an elegant solution with a direct approach.
Some of the features include:
* Connect to any XMPP 1.0 server (Google Talk, LJ Talk, jabber.org, etc)
* Supports TLS encryption
* Several XML processing approaches and supported styles (process indefinitely, processUntil an event, processTime for a number of seconds), waiting on events or map them, etc.
* Persistent connections (AJAX Web client anyone?)