The last several days were.. filled with activity – gathering data and preparing a paper submission to MICRO-40. It’s my first time to submit a paper, and it’s mostly the research I did during the Masters portion of the degree, so it’ll be interesting to see how things work out.

Yay for screen multiplexing! Perhaps it’s more useful for my 12″ iBook G4, but ssh + screen to keep console sessions running from a single terminal is very useful when moving around remotely. Add in vim‘s own document splitting.. I’ve got 10+ virtual windows with many more subwindows to edit scripts like crazy. All this is going on with X windows opening and closing as tests start and finish…

After 100s of emails and last minute changes.. time for a nap.

Running a ton of tests remotely – X windows everywhere!

Status Update:

[Code] Got automatic hash checking working in the channel so it gives an error status on Link Fingerprint failure, so loading bad hash pages results in an error page, and some images (gif, bmp) show up as a broken image.. others like jpg progressively load and show whatever they have on failure (i.e., the whole thing).

[RFCs] Looking into other #fragment-id uses (XML XPointers and PDF) and references from Wilde and Baschnagel’s text/plain paper in HT 2005 (Sixteenth ACM Conference on Hypertext and Hypermedia).

Last week (2007/05/27 – 2007/06/02):

– Implement hash comparisons and pass on an error code from OnStopRequest to listeners downstream
– Add a new network error pages for Link Fingerprint failures on page view (need a better string..)
– Discuss implementation details on m.d.t.network clarifying my current implementation just provides a new error code after the transfer finishes
– Attend Google Dev Day (Thursday)
– Invite Erik Wilde to discuss RFC stuff and Link Fingerprint issues
– Begin handling of Link Fingerprint failures in the consumers like download manager (vs webbrowserpersist/exthandler)

This week (2007/06/03 – 2007/06/09):

– Remove/delete failed downloads cleanly from the download manager
– Refactor added code in HttpChannel so adding Link Fingerprints to other channels is clean/simple
– Look into the image library to handle Link Fingerprint transfer failures
– Figure out what interfaces to provide (for extensions) e.g., exist?/get fingerprint from URI, check fingerprint against file/stream
– Note: Next week I’ll be out – attending FCRC 2007 in San Diego 9th to 13th

Today was quite exciting with Google’s event in San Jose. I got to learn about the new Google APIs and developer tools that’ll be pushing forward web applications as well as to meet all sorts of people and see what they’re working on. I attended most of the main sessions except to participate in the Fireside Chat for Google Gears, but the nice thing is that many of the sessions were recorded and are now available on youtube [code.google.com].

Overall, the event was very Google. Colorful decorations with beanbag seats and exercise balls. Free drinks. Free food. Free swag. And plenty of Google products. (Tons of Dev Day photos [picasaweb.google.com].)

Free Developer Day T-shirts + badge

I found the performance improvements provided by Google Gears especially interesting because one doesn’t have to even be offline to see some benefits (of removing network latency). At the fireside chat, I asked a question about Javascript performance (relating to my research area) because Gears will facilitate building more complex web apps that do a lot more (distributed) processing on the client. The responses were valid in that bottlenecks do come from updating the DOM and disk I/O, but maybe I was just hoping to hear what Google has planned in pushing Javascript from interpreted to JIT and then adaptive optimizations.

And after the conference part ended, there was a big party at the Googleplex with even more free food and beverages. The center of the campus had food stands with hamburgers, corn dogs, shaved ice, cotton candy, churros, nachos, and a bunch more. The dining area of the main cafeteria changed into a party area with a DJ, pool tables, arcade games, and flashing lights with the projector showing photos of Dev Day around the world.

When it started getting dark, they brought out some neat cups to add to the party atmosphere – glowsticks in a cup form. Basically, cups that glow, so you end up drinking glowing green goo in the dark.. kinda. Just make sure when you hit the cup against a hard surface to break the glow capsules, don’t hit so hard that you crack the cup causing the liquids to spill out.

“Cracked” glow-cup (only the middle red one is glowing)

Flash shows the cups’ true color