To me, the secret in building systems that rock, no, better yet, monster systems, is all in the *blend*. I don't buy the silver bullet, floor wax *and* dessert topping single focussed story lines that fashionably spill out from time to time inevitably resulting in misdirected project churn regardless as to the best of intentions. Such tactics are often enamoured deeply with one or another flavor of the day solutions that might sing and dance like a champ in the lab but upon release in the wild tend to not have the legs to get up and run let alone walk a straight line during 9 to 5 working hours.
What catches my eye is rock solid logically blended strategies seeing, first hand, that such systems tend to adapt more organically, have staying power and are, frankly, a kick in the pants to construct and cultivate ... the last of which is likey the primary reason such systems thrive.
As such, I wanted to point out a cool JXTA sighting that is truly blended(tm). Daniel Elenius completed his initial work on a JXTA/DAML-S integeration project which is ...
... basically a framework ... to let JXTA peers described their services semantically using DAML-S and WSDL, and search/use each others services (using JXTA-SOAP, and reasoning in JTP).
Upon digging a bit into Daniel's work a bit further I noticed he is using an AI package authored by a colleague of mine during a "start up gig I did back in the day." I've always wanted to play more with fuzzy logic/AI'ish system and every time I run across blended systems such as this I smile knowing the app infrastructure bar is continually rising.
It's all in the blend.
JXTA == network independence
Secure End-to-End Computing
in my ears: Moby/Moby 18 B Sides/ISS