Geekpage has a terrific interview with HTTP 2.0 WG chair Mark Nottingham on recent developments relating to HTTP 2.o. The newly released IETF draft is at http://tools.ietf.org/html/draft-ietf-httpbis-http2-04.
A few minutes ago, Tim Berners-Lee announced that as of June 1, Daniel Appelquist and Peter Linss will take over as chairs of the W3C Technical Architecture Group. I have been a member of the TAG since 2004 and chair since early 2009. Serving on and chairing the TAG has been one of the most exciting and rewarding things I’ve done, and I’m extraordinarily grateful that Tim and the TAG have given me the opportunity.
My current appointment would have run for a few more months, but the TAG is in the process of resetting its agenda and priorities for the next two years. Bringing in Peter and Dan now gives them opportunity to help the TAG plan as well as deliver this work. To free space for our new chairs, I will resign my position on the day they join. I will attend the TAG’s upcoming meeting in London and I expect to continue to work informally with the TAG and the new chairs over the next few months.
This is a particularly exciting time for the TAG and if we had not needed “my” slot for our new chairs, I would have been happy to continue. I have particularly enjoyed working with and learning from our new members, many of whom play key roles in the development of the most important new Web technologies such as HTML5, AJAX-style Web Apps, mobile Web apps, etc. Nonetheless, I am delighted that this change is happening. My teaching responsibilities are increasingly taking time that would otherwise go to the TAG, and have prevented me from traveling to some overseas W3C meetings. More important, Tim’s choice of Peter and Dan to replace me is in my opinion brilliant. We are very lucky to have them, and now is the perfect time for them to take over.
My warm thanks to all the TAG members past and present who have made my time on the TAG such a pleasure. I look forward to working informally with the W3C and the TAG in the future.
I’m pleased to announce that I have accepted a position as Professor of the Practice in the Tufts University Department of Computer Science. I expect to be teaching a course each term and advising students. As I said in my previous post, I’ve been having a wonderful time at Tufts, and I’m thrilled to have the opportunity to teach there in coming years.
If you’re wondering why I haven’t posted since September, it’s because I’ve been working nonstop on teaching my distributed systems course at Tufts. I’ve had a terrific time, and we had a wonderful group of students. Though he’d probably be surprised to hear it, the original inspiration for this course came from Tim Bray. We were sitting together at some meeting or other probably 14 years ago and he said to me: “you know, it would be great if someone taught a distributed systems course based on the Web.” The idea stuck with me, and when the opportunity came to teach at Tufts, I decided to give it a try.
There are always rough edges teaching a new course, but overall I’m really pleased with how it turned out. If you’re interested in what we covered, check out the Lectures Page , and especially the Principles Page, which gives a summary of the key points covered in the course.
The good news for me is that it looks like I will be back at Tufts this spring, and quite possibly in coming years as well. I’m delighted! Details to follow. Thanks to everyone who’s made me so welcome at Tufts!
After spending all summer preparing, my new Tufts course on Internet-scale Distributed systems starts this week. I’m excited! There’s still plenty of work to do on the details, but the course Web page is now up, and I expect that course notes, slides etc. will start appearing there as things unfold.
I’m delighted to announce that I have accepted a position as a Visiting Scholar in the Computer Science Department at Tufts University, and in fall of 2012, I will be teaching a new course titled: Internet-Scale Distributed Systems: Lessons from the World Wide Web.
The course description is:
The World Wide Web, one of the most important developments of our time, is a unique and in many ways innovative distributed system. This course will explore the design decisions that enabled the Web’s success, and from those will derive important and sometimes surprising principles for the design of other modern distributed systems.
We will introduce and draw comparisons with more traditional distributed system designs, including distributed objects, client/server, pub/sub, reliable queuing, etc. We will also study a few (easily understood) research papers and some of the core specifications of the Web. Specific topics to be covered include: global uniform naming; location-independence; layering and leaky abstractions; end-to-end arguments and decentralized innovation; Metcalfe’s law and network effects; extensibility and evolution of distributed systems; declarative vs. procedural languages; Postel’s law; caching; and HTML/XML/JSON document-based computing vs. RPC.
The purpose of this course is not to teach Web site development, but rather to explore lessons in system design that can be applied to any complex software system.
Everyone I’ve met from Tufts, both students and faculty, loves it there, and I’m very excited to have this opportunity to join them!
Awhile ago I posted an entry recommending a Nice Video about Colossus and Tommy Flowers. I have since been in touch with Capt. Jerry Roberts, who was one of the key members of the codebreaking team at Bletchley Park (B.P) during World War II. Capt. Roberts contacted me after I made my posting, and although he’s delighted to see the increasing recognition that’s coming to so much of the vital work done at B.P., he did have some concerns about details in the video.
In an e-mail to me, he made the following points (all quotations are directly from him…the “Testery“, mentioned in the quotes below, was the section of B.P. devoted to daily breaking of the message encipher on Tunny code, which was used by the German high command, including Adolph Hitler himself):
- “Colossus was built with one purpose only – to assist the Testery in speeding up one stage (breaking the chi wheel) of the breaking of Tunny, but the rest of the stages were still worked out by hand in the Testery by codebreakers and support staff. Without Bill Tutte breaking the Tunny-system, without the Testery daily breaking of Tunny, there would have been no need for Colossus at all.”
- The video compares the performance achieved using Colossus with the previous approach, which was to do the codebreaking entirely by hand. “They said [in the video] a message took 6 – 8 weeks to break the wheel patterns by hand; in fact we normally broke within 6 to 8 hours (within a shift); rarely, up to 16 hours might have been required. I know, I was a leading codebreaker doing this breaking all that time. Prof. Jack Copeland also quotes it as inside 8 hours, normally.”
- “From mid 1942 to mid 43 for the whole year, the Testery was breaking Tunny messages without any machine help (all by hand), included the messages relating to the Battle of Kursk – biggest tank Battle ever. Even when Colossus came later in spring 1944, still most work was done by hand in the Testery. The Testery broke 90% all the traffic handled on Tunny. The Newmanry (handled machinery – Robinsons and Colossuses) did 20 to 25% of the workload, and Testery did 75% at least. However, there is nothing about these inside information at B.P, as they are more keen to show off the machinery. “
By the way, Capt. Roberts remains very active in helping to promote recognition for all the good work done at Bletchley, and he is a terrific speaker. His belief (and the belief of many others) is that “Enigma decrypts helped Britain not to lose the War in 1941. Tunny decrypts helped shorten the European War by at least 2 years.”
Several years ago, before I realized we had mutual friends, I posted an entry recommending one of Capt. Roberts’ talks at UCL.
Note: this posting was updated on 27 June 2012 with minor corrections and annotations from Capt. Roberts, who was kind enough to review my original version.
IBM and CDC developed some of the most innovative computer architectures during the 1960′s. The advanced 360 architectures such as the IBM 360/91 are well known for their pioneering implementations of instruction-level parallelism and register renaming. Before that, Project Stretch was famous for contributing many innovations to computer architecture. Less well known was the Advanced Computing System (ACS), a no holds barred effort started in 1961 to build the fastest possible computer. Leading computer designers including Gene Amdahl, as well as my (later to be) friends from IBM: John Cocke, Fran Allen, and Harwood Kolsky came together to build this machine, which was eventually abandoned in 1969. Amdahl went on to found Amdahl Corporation, and John and Fran later won Turing awards, John’s for the invention of RISC architecture, and Fran’s for her pioneering work on compilers.
There’s a nice Web page up with a brief history of the ACS, and a video to a Computer History Museum video of a Feb. 2010 ACS reunion meeting. ACS pioneered many important features including instruction pre-fetch and dynamic out-of-order execution. The Web page and video are worth checking out if you’re interested in the history of computer architecture.
(Thanks to Lynn Wheeler for the link to the ACS page.)
It’s that time of year again, and audio mastering engineer Ian Davis is reminding us to celebrate “Dynamic Range Day“. This is about improving the sound of the audio recordings that we buy on CD and stream through the Internet. Specifically, it’s about compression. Read the rest of this entry »
Google has posted a nice little video about Bletchley Park and the Colossus machine, including nice remembrances of hardware designer Tommy Flowers. There’s also a posting about Tommy Flowers in the Google blog.
I had the opportunity to see the reconstruction of Colossus in operation, breaking actual codes, when I visited the British National Museum of Computing last year. “Lynetter” has posted to Youtube a video introduction to the reconstructed machine and also video of the late Tony Sale showing the reconstruction in operation. Unfortunately, when I visited, Tony had just recently died.
One twist on all this struck me as interesting: when Colossus was (partially) declassified in the mid 1970′s, books like The Ultra Secret claimed that it was used to break the German enigma code. Recently, more information has been declassified, and it’s now clear that’s wrong. The British did break the enigma at Bletchley park using a machine known as the Bombe. The Bombe (not bomb!) was not an electronic digital computer and it did not use valves (what we Americans call vacuum tubes). The Bombe was built of technology similar to old phone company rotary stepping switches and relays. Patch panels encoded information relating to the keys to be broken, and the switches would rotate through all possible positions until patterns suggesting a possible key match were detected. The switches would then stop in position, and from the final positions keys could be determined.
The enigma was used to encipher field and naval communications. In fact, we now know that Colossus, which was an electronic computer using large numbers of “valves” (along with relays, high speed paper tape, etc.) was built specifically to crack the much more difficult Lorenz cipher, which was used by the German high command. The British were thus able to decrypt traffic going to and from Adolf Hitler himself.
Many people have commented on the pros and cons of the New York Times paywall. Most of these comments debate the effectiveness of the paywall in meeting the Times’ financial goals, discuss ways in which users will circumvent the paywall, etc. Here I’d like to explore a different issue: it seems to me that the paywall, as currently implemented, violates the specifications for the Web’s HTTP protocol. Interestingly, my concern is not with the part of the system that charges readers, it’s with the part the tries to count the 20 free pages allowed per month.
I’m hoping to do more book reviews here, as I’ve been doing quite a bit of reading this year. So, here’s one to get started…
The first war of physics : the secret history of the atom bomb, 1939-1949 [ISBN: 1605981974] by Jim Baggott is an excellent history of the physics, politics, wartime events and espionage that all contributed to the remarkable history of the bomb. This is a moderately long book, but very readable, even gripping (well, I like this stuff). Very highly recommended for anyone with an interest in 20th century history, military history, or the history of technology. The physics is explained in readable terms, in the few places where it’s important to the story, but no technical background at all is required to appreciate this important book. Again, very highly recommended.
Note that the first 2/3 of the talk is a very interesting exploration of the security characteristics of Bitcoin, also showing how the Bitcoin database can be used as a peristent shared store. The latter third of the talk introduces Dan’s tools for detecting artificial delays introduced by ISPs.
I have gotten out of the habit of announcing all of our Rock City Band appearances here on the blog, in part because I’m now keeping a mailing list for those who are interested. May is a particularly busy month for us, with four appearances coming up, so I thought I’d make an exception and post again here. We’ll be appearing:
May 7 (this Sat): Princeton Station, in Chelmsford, MA (on Route 4, just east of Route 3)
May 13 & 14: The Haluwa Lounge, in Nashua, NH (in the Nashua Mall, exit 6 off Route 3)
May 28: Back at Princeton Station one more time
All shows start at 9 PM, and there’s no cover at either Princeton or the Haluwa. I expect to be playing bass all four nights.
If you’d like to be on the mailing list to get announcements of all our gigs, please e-mail me at “blogmaster AT arcanedomain DOT com”, making the obvious substitutions for AT and DOT.
One of the excuses that’s been trotted out by several commentators in defense of the New York Times paywall is that it’s “just like public radio”. Well, no. When I contribute to public radio, which I do, my contribution helps make all of that content freely available to everyone. If I “contribute” to the New York Times paywall, I’m buying myself access, and supporting a model in which valuable Web content is only available to those who can afford it.