Tag Archives: web

Sciveram vicipaediam linguis barbaris (exempli gratia anglice, francice, et ceteris) legi potere, sed non latine. Iam tenet super duo milia articulorum. Quid artis!

A short while ago, I reluctantly acknowledged that RSS 2.0 will likely fill the same role for data that HTML fills for documents, providing a single, shared format across the web (the big missing piece of the puzzle for REST … Continue reading →

I noticed today that Gmail is now offering an alternative, non-AJAX interface, selectable by choosing “basic HTML” below the message listing. This is actually a great opportunity to experiment and see whether AJAX (or any other kind of heavy DHTML-style … Continue reading →

Coordinator: Crucifixion? Prisoner: Er, no, freedom actually. Coordinator: What? Prisoner: Yeah, they said I hadn’t done anything and I could go and live on an island somewhere. Coordinator: Oh I say, that’s very nice. Well, off you go then. Prisoner: … Continue reading →

As I’ve mentioned before, REST offloads complexity from the protocol (HTTP) to the content (XML). That makes REST look simple as long as you focus only on the protocol, but RESTafarians cannot get away forever with leaving the content format … Continue reading →

There’s a lot of noise about AJAX recently, ranging from positive to negative to what’s the big deal? It’s true that architecturally, AJAX is nothing new — basically, it’s just the old, pre-Web client-server model wrapped up in the browser … Continue reading →

Via Anne van Kesteren (again), I have found a site with a pure-CSS rendition of the Canadian flag (the image here in my blog is a screenshot, not the live CSS). It’s a little squished, granted, but at least it’s … Continue reading →

[Update: partial contact information at bottom.] Yesterday I found out about a major government XML+HTTP (i.e. REST) web application that has been open to the general public since October 2004 but was never formally announced — I’m posting about it … Continue reading →

[Update: why this has to do with REST] Here is the fourth in a series of REST design questions: how much should the XML data files returned by a REST web application be normalized into separate XML files? For example, … Continue reading →