I guess there’s no harm in an occasional links+commentary dump; after all, everybody does it. Item: Bits at the Edge is the blog of Motorola CTO Padmasree Warrior. The entries are too long and dip into marketing-speak, but there’s good writing and original thought in there too and I’ve subscribed. How could anyone in computing not need to know what Motorola’s CTO is thinking? Item: Via Joe Gregorio, PDF slideware on The EBay Architecture. This ought to be required reading for everyone in this business whose title contains the words “Web” or “Architect”. I wonder if this sort of wisdom is being taught in universities? Item: Advanced Message Queuing Protocol (AMQP) Specifications has crossed my radar a few times recently. If you really believe in loose coupling and asynchronous messaging (as we all claim to), then you believe in something like this. Item: How to find out which font has which characters; something I’ve never known how to do on OS X. Item: Ugandans grab ‘pig-for-name’ deal; it’s hard not to have complicated feelings about this one.
Comment feed for ongoing:
From: Sylvain Hellegouarch (Dec 17 2006, at 23:46)
How does AMPQ relate to XMPP? What are the benefits or drawbacks?
[link]
From: Manuzhai (Dec 18 2006, at 07:12)
There's an article at http://antecipate.blogspot.com/2006/07/what-is-so-advanced-in-amqp.html about AMQP and its relation to XMPP. I find the author to be, well, a little whiny at times, but in this post he seems to be right on the money.
If you really believe in loose coupling and asynchronous messaging and open standards, why not go with the IETF-standardized XMPP? It's a pretty great protocol (I've worked through the RFC's and implemented parts of a client library to see how it works out: it works out just fine).
[link]
From: Sylvain Hellegouarch (Dec 23 2006, at 01:36)
Thanks fo the link. Indeed I went for XMPP as well as I fail to grasp what AMQP brings over XMPP that could not be solved with the latter anyway.
[link]