Wednesday, June 12, 2002

Blogging and homeland security: connecting the dots. Sunday's New York Times featured a disturbing story on the IT culture clash between Google and the FBI: ... 8:43:02 AM

What if being non-communicative weren't an option?. This Fortune article on Esther Dyson was cited on a private mailing list. It's interesting to see where she is placing bets: ... 8:17:19 AM

Matt Pope on the Groove experiment: reaching closure. Matt Pope reflects on the recent Groove experiment: ... 8:17:19 AM

Radio supports XCOPY deployment. Kevin Altis ran into some admin trouble with Radio: ... 8:17:18 AM

Ruby (the language), TupleSpaces, REST, and Ruby (Sam). I wish I could point to an article by Dave Thomas and Andy Hunt in the April issue of Linux Magazine, because it has a beautiful example of a chat system done using Ruby's tuplespace and drb (distributed Ruby). I'll link to it when it posts. Here's what reminded me of it: ... 8:17:18 AM

This phase of the Groove/weblog experiment is concluding. The Groove/weblog experiment has run its natural course. Jeroen plans to shut down the space. He writes: ... 8:17:18 AM

But part of the potential of WS-Security is to be able to have an authenticated (and possibly signed) transmission without having to encrypt the entire message.  Important, I think, for both the point-to-point case and with intermediaries.[Greg Reinacker's Weblog] Certainly important for the intermediary case, not sure about the point-to-point case, the only thing it seems to buy you is a consistent approach with the approach required for intermediaries. Its going to cost you though at run time, I guess it'll be a while before a WS-Security implementation has been tuned to the level current SSL implementations have. SSL also has the advantage of being able to amortize the cost of establishing the session key over multiple message exchanges, via HTTP persistent connections. 8:17:01 AM

Cool!, the SUN folks have put up a SOAP interop server. 8:17:01 AM

I've updated the web services security story with some input from Justin Rudd. [Greg Reinacker's Weblog] Putting credentials in a SOAP header without an ecrypted channel is a waste of time, but if you have an encrypted channel, you might as well use the channel's authentication support. WS-Security only starts to make sense [much the same as SOAP] when you have intermediaries. 8:17:01 AM