Loosely Coupled

I've spent a lot of time away from the office lately and haven't had much of a chance to post. Here's a quick update on what I've been thinking about. First off, the Ruby XMPP-bot I had started is complete. This was insanely easy to implement in Ruby. The only snag I ran into was in creating a new chat room with the bot. The 0.3.1 release of XMPP4R seems to hang when creating a new room. After some research , it was apparent that others experienced this problem and had already submitted a patch. Cool. My next job is to connect the bot to an application my company developed. Communication to this module has been done previously using CORBA. Unfortunately (or not), I have not been able to find an acceptable Ruby CORBA module ( Rinn looks like it's dead and R2CORBA does not appear mature enough). Recently many of our legacy CORBA API's have been replaced with Web Service API's and I'm going to take this approach with this module. While researchi

I've been hearing a lot of buzz about QEDWiki, which is being developed at IBM. QEDWiki is a basically a wiki that can host simple web components. At first glance, QEDWiki looks like a typical portal, displaying aggregated information from around the web in widgets. Think dashboards like PageFlakes or My Yahoo . I soon learned that QEDWiki is something completely different. My perception changed when I saw these widgets linked together, creating what IBM calls "situational applications". A "situational application" is a simple applications created on the fly using information provided through a web service. These applications can be created by business users, for business users - without the support of a development team - very much like the advanced Excel applications created and shared today by business teams. I see something like QEDWiki taking the place of these apps with Service Oriented Architectures (SOA) playing the role of the Excel "s