Tuesday, 19 December 2023RFC 9518: Centralization, Decentralization, and Internet Standards has been published, after more than two years of review, discussion, and revision.
Wednesday, 22 June 2022Most of the complexity and nuance of the Web is stuffed into browser engines. Even though they’re a huge burden to develop and maintain, the world is lucky enough to have three major ones, and they’re all Open Source.
Wednesday, 8 June 2022The HTTP “core” documents were published on Monday, including a revision of HTTP semantics, caching, HTTP/1.1, HTTP/2, and the brand-new HTTP/3. However, that’s not all that the HTTP community has been up to.
Monday, 6 June 2022Seven and a half years ago, I wrote that RFC2616 is dead, replaced by RFCs 7230-5.
Thursday, 18 February 2021Today, Facebook shut off the news in Australia – all of it, and much more besides. For example, when I tried to post a link to this blog entry on Facebook, they responded:
Friday, 22 April 2016The implicit goal for Web performance is to reduce end-user perceived latency; to get the page in front of the user and interactive as soon as possible.
Tuesday, 18 August 2015One of the things that came up at the HTTP Workshop was “distributed HTTP” — i.e., moving the Web from a client/server model to a more distributed one. This week, Brewster Khale (of Archive.org fame) talked about similar thoughts on his blog and at CCC. If you haven’t seen that yet, I’d highly suggest watching the latter.
Wednesday, 18 February 2015The IESG has formally approved the HTTP/2 and HPACK specifications, and they’re on their way to the RFC Editor, where they’ll soon be assigned RFC numbers, go through some editorial processes, and be published.
Saturday, 27 December 2014A few months ago I went to the Internet Governance Forum, looking to understand more about the IGF and its attendees. One of the things I learned there was a different definition of “intermediary” — one that I think the standards community should pay close attention to.
Saturday, 27 December 2014Python 2.7.9 was recently released, and that means that it supports TLS Server Name Indication.
Thursday, 4 December 2014This post is mostly for folks who haven’t been following Web standards closely — especially IETF folks. If you have been, there’s probably not much new here (but feel free to poke holes!).
Saturday, 7 June 2014Don’t use RFC2616. Delete it from your hard drives, bookmarks, and burn (or responsibly recycle) any copies that are printed out.
Sunday, 1 June 2014Chrome is looking at adding support for RFC5861’s stale-while-revalidate, which is really cool. I wrote about the details of SwR when it first became an RFC, but its application to browsers is something that’s a new. Seems like a good time to answer a few potential questions.
Friday, 9 May 2014When TLS was defined, it didn’t allow more than one hostname to be available on a single IP address / port pair, leading to “virtual hosting” issues; each Web site (for example) now requires a dedicated IP address.
Monday, 17 March 2014The IETF now considers “pervasive monitoring” to be an attack. As Snowden points out, one of the more effective ways to combat it is to use encryption everywhere you can, and “opportunistic encryption” keeps on coming up as one way to help that.
Thursday, 30 January 2014HTTP/2 is getting close to being real, with lots of discussions and more implementations popping up every week. What does a new version of the Web’s protocol mean for you? Here are some early answers:
Tuesday, 4 December 2012One of the most vexing problems that still seems to be facing people when I talk to them about HTTP APIs is how to handle versioning and extensibility – i.e., how they evolve.
Wednesday, 5 September 2012A common problem for APIs is partial update; when the client wants to change just one part of a resource’s state. For example, imagine that you’ve got a JSON representation of your widget resource that looks like:
Saturday, 4 August 2012The HTTPBIS Working Group is in a transitional phase; we’re rapidly finishing our revision of the HTTP/1.1 specification and just getting steam up on our next target, HTTP/2.0.
Tuesday, 17 April 2012Erik Wilde - otherwise known as dret - has published an Internet-Draft for a “profile” link relation type:
Saturday, 14 April 2012When you’re designing HTTP APIs, you need to keep a lot of concerns in mind. Stealing a page from XP, let’s look at some possible personas and their user stories for HTTP-based APIs:
Friday, 13 April 2012When people create HTTP APIs, one of the common decisions is about what format to use, usually revolving around “JSON or XML?”
Friday, 25 November 2011To be a full-fledged format on the Web, you need to support links – something sorely missing in JSON, which many have noticed lately.
Friday, 21 October 2011More than ten years ago, I was working at Akamai and got involved in the specification of Edge Side Includes (ESI), sort of a templating language for intermediaries.
Wednesday, 12 October 2011Since joining Rackspace to help out with OpenStack, one of the hot topics of conversation I’ve been involved in has been extensibility and versioning.
Friday, 2 September 2011HTTPbis published RFC6266 a little while ago, but the work isn’t finished.
Sunday, 28 August 2011In discussing my whinge about AppCache offline with a few browser vendory folks, I ending up writing down my longstanding wishlist for making browser caches better. Without further ado, a bunch of blue-sky ideas;
Wednesday, 24 August 2011It used to be that when you registered a media type, a URI scheme, a HTTP header or another protocol element on the Internet, it was an opaque string that was a unique identifier, nothing more.
Friday, 5 August 2011Last week, Blaze.io highlighted how mobile browsers use HTTP pipelining.
Wednesday, 27 July 2011FYI, I’ve implemented Content Security Policy on this site. If your’e a Mozilla user, please tell me if you have any problems.
Monday, 11 July 2011The explosion of HTTP implementations isn’t just in clients and servers. An oft-overlooked but important part of the Web ecosystem is the intermediary, often called just a “proxy”*.
Sunday, 19 June 2011HTML5’s AppCache mechanism is one confused little puppy. Purporting to be for taking web applications offline — a compelling and useful thing — it’s more often used by performance-hungry sites that want to use it as an online cache.
Friday, 27 May 2011After designing and deploying Cache Channels, it quickly became apparent that one Web cache invalidation mechanism wasn’t able to cover the breadth of use cases.
Wednesday, 18 May 2011A lot of people seem to be talking about and performing load tests on HTTP servers, perhaps because there’s a lot more choice of servers these days.
Tuesday, 22 March 2011Now, you can test any URL to instantly determine if it’s RESTful.
Tuesday, 1 March 2011The IESG has received a request from the Hypertext Transfer Protocol Bis WG (httpbis) to consider the following document:
Friday, 1 October 2010I’m going to try to start blogging more updates (kick me if I don’t!) about what’s happening in the world of HTTP.
Friday, 23 July 2010Since SPDY has surfaced, one of the oft-repeated topics has been its use of TLS; namely that the SPDY guys have said that they’ll require all traffic to go over it. Mike Belshe dives into all of the details in a new blog entry, but his summary is simple: “users want it.”
Thursday, 3 June 2010A while back we used an absurd amount of reward points from our credit card to get some Myer gift certificates, and on the weekend these miraculously turned into a new TV, the Sony 32EX600.
Thursday, 6 May 2010On a bit of a roll, RFC5861: HTTP Stale Controls has (finally) been published as an Informational RFC.
Wednesday, 5 May 2010Steve Souders and others have been working for a while on HAR, a HTTP Archive format.
Wednesday, 7 April 2010One of the nagging theoretical problems in the Web architecture has been finding so-called “site-wide metadata”; i.e., finding something out about a Web site before you access it. We wrestled with this in P3P way back when, and the TAG took it up after that.
Wednesday, 10 March 2010Thomas Hühn has graciously translated the caching tutorial into German. Thanks!
Friday, 15 January 2010If you haven’t seen it already, check out the Call for Papers for the First International Workshop on RESTful Design (WS-REST 2010), where I’m on the program committee, along with many of the usual suspects.
Wednesday, 16 December 2009Australia has apparently decided, through its elected leaders, to filter its own Internet connection.
Friday, 13 November 2009A couple of nights ago, I had a casual chat with Google’s Mike Belshe, who gave me a preview of how their “ Let’s make the Web faster” effort looks at HTTP itself.
Friday, 30 October 2009A long time ago*, the word in high-performance proxy-caching was Inktomi’s Traffic Server. It was so fast it was referred to being “carrier grade” and this could be said without people smirking, and it was deployed by the likes of AOL, when AOL was still how most people accessed the Internet.
Thursday, 13 August 2009Although I’m a bit concerned to see so many references to “Web 2.0”, it’s very exciting to see Australia talking about opening up government.
Friday, 3 July 2009The Stockholm IETF meeting is shaping up to be an interesting one (and not just because it’s in such a beautiful city).
Thursday, 25 June 2009A (very) long time ago, I wrote the Cacheability Engine to help people figure out how a Web cache would treat their sites. It has a few bugs, but is generally useful for that purpose.
Wednesday, 17 June 2009The caching tutorial is now available in Chinese, courtesy of Che Dong (and apologies for taking so long in linking to it!).
Friday, 12 June 2009Part of my job is maintaining Yahoo!’s build of Squid and supporting its users, which use it to serve everything from the internal Web services that make sites go to serving Flickr’s images.
Friday, 5 June 2009HTTP performance is a hot topic these days, so it’s interesting that Opera has announced a “turbo” feature in Opera 10 Beta;
Friday, 29 May 2009Everybody’s atwitter (yeah, sue me) about the Google Wave developer preview. Lots of new stuff there, but for me the most revealing comment, almost a throwaway, was here:
Tuesday, 14 April 2009I had a lovely holiday weekend in Canberra with the family, without Web access. Perhaps I’ll blog about that soon — Canberra being in my opinion one of the nicest overlooked cities in the world — but that will have to wait. Going offline for a few days always brings a certain dread of what one’s inbox will hold when you get back, and this one was no exception.
Tuesday, 24 February 2009There’s a rule of thumb about when a HTTP response can be cached; the Caching Tutorial says:
Wednesday, 18 February 2009UPDATE: RFC6648 is now the official word on this topic.
Friday, 21 November 2008There are lots of new “Web 2.0” specs emerging — many beginning with “o” — that are both exciting and concerning.
Monday, 27 October 2008Ryan Tomayko announces Rack::Cache, a HTTP cache for Ruby’s generic Web API;
Thursday, 16 October 2008Metadata discovery is a nagging problem that’s been hanging around the Web for a while. There have been a few stabs at this problem (including at least one by yours truly), but no real progress.
Friday, 4 July 2008Here’s a gem on a little-used mailing list:
Thursday, 20 March 2008Having complained before about the sad state of HTTP APIs, I’m somewhat happy to say that people seem to be getting it, producing more capable server-side and client-side tools for exposing the full range of the protocol; some frameworks are even starting to align object models with resource models, where HTTP methods map to method calls on things with identity. Good stuff.
Monday, 3 March 2008Not many people that I know outside of IETF circles realise that a new *DAV effort has started up; CardDAV.
Sunday, 17 February 2008It’s 7am, I’m sitting in the Auckland Koru Club on my way home and reading the minor kerfuffle regarding PATCH with interest.
Wednesday, 6 February 2008Here’s one that I’ve been wondering about for a while, for the LazyWeb (HTTP Geek Edition);
Monday, 21 January 2008I’m following the discussion of RESTful Web description in general, and WADL in particular, with both difficulty and interest (see Patrick and Joe’s thoughts for a nice contrast).
Friday, 4 January 2008The stale-while-revalidate and stale-if-error extensions aren’t the only fiddling we’ve been doing with the HTTP caching model. Now that Squid 2.7 is starting to see daylight, I can explain about a much more ambitious project — Cache Channels.
Wednesday, 12 December 2007We use caching extensively inside Yahoo! to improve scalability, latency and availability for back-end HTTP services, as I’ve discussed before.
Sunday, 9 December 2007I haven’t talked about it here much, but I’ve spent a fair amount of time over the last year and a half working with people in the IETF to get RFC2616 — the HTTP specification — revised.
Friday, 2 November 2007I’ve updated the WADL documentation stylesheet, primarily to;
Saturday, 8 September 2007Feed Paging and Archiving (nee Feed History) has finally made it to a standards-track RFC.
Tuesday, 7 August 2007I’ve been hoping to avoid this, but ETags seem to be popping up more and more often recently. For whatever reason, people latch onto them as a litmus test for RESTfulness, as the defining factor of HTTP’s caching model, and much more.
Saturday, 28 July 2007URI Templates -01 is now an Internet-Draft.
Wednesday, 20 June 2007A while back I wrote up the state of browser caching, after writing a quick-and-dirty XHR-based test page, with the idea that if people know how their content is handled by common implementations, they’d be able to trust caches a bit more.
Wednesday, 13 June 2007It’s a little thing, but I’m very pleased to see that Safari 3 will check with you before you discard a page where you’ve entered data on a form.
Sunday, 29 April 2007The QCon presentation ( slides) was ostensibly about how we use HTTP for services within Yahoo’s Media Group. When I started thinking about the talk, however, I quickly concluded that everyone’s heard enough about the high-level benefits of HTTP and not nearly enough details of what it does on the ground. So, I decided to concentrate on one aspect of the value that we get from using HTTP for services; intermediation, as an example.
Thursday, 5 April 2007We’ve announced the program for this years’ Developers’ Track, and I’m very excited about the lineup.
Tuesday, 27 February 2007I think that most of the debate about REST focuses on the wrong things, leading developers down the garden path at the expense of their productivity and the success of their projects. Time and time again, I’ve seen folks who are new to REST get caught up on small stuff like this;
Wednesday, 7 February 2007Yahoo! (finally!) released Pipes as a beta today; congrats to the very talented team that put this together.
Wednesday, 7 February 2007A reminder: proposals for the Developers’ Track at WWW2007 should be in by February 16th.
Thursday, 30 November 2006One of the perceived deficiencies of JSON is that it doesn’t have a schema language. I say “perceived” because the problems that a schema language brings often outweigh the benefits; after all, look at the mess that XML Schema is in.
Friday, 27 October 2006There are plenty of reasons to hate HTTP Cookies, but there’s one thing that especially annoys me; their syntax.
Thursday, 19 October 2006Dave Johnson writes up a nice summary of the issues of adding new elements to HTML for declarative Ajax, something that I ran into when doing HInclude.
Tuesday, 17 October 2006My team at Yahoo! is looking for a mid-level developer (5-10 years experience) to help build our HTTP/REST toolkit, among other things.
Friday, 13 October 2006A couple of interesting things have happened recently; first, Jonathan Marsh has a new job;
Wednesday, 4 October 2006As mentioned a while back, there are a variety of places where it would be useful to be able to describe the structure of a URI, rather than just convey a URI itself. I took a stab at this in the Link Header draft, and have also been working in the background with DeWitt Clinton, Joe Gregorio, Marc Hadley, Dave Orchard, and James Snell on a more general specification, URI Templates, the first draft of which we (finally!) got published today.
Sunday, 1 October 2006Hot on the heels of the last batch, Stefan pointed me to Jesse Skinner’s addDOMLoadEvent, which seems to avoid the problems I found earlier (you know you’re in for some debugging when you’re cutting-and-pasting code from blog comments!).
Thursday, 28 September 2006I’ve updated the url_template.js and json_form.js libraries to fix some bugs, to make the demo I gave at XTech run more smoothly. It should work well on Safari, Mozilla and IE6 (despite some glitches at a showing inside Y! the other day; the demo gods were not smiling). It does not work in Opera; it seems like the more I use XHR in that browser, the more bugs I find. I’m thinking of updating the XHR tests to catch more of them, but it’s a fair amount of work.
Saturday, 16 September 2006Apple’s shipping an iSight camera in just about everything these days, and one of the coolest apps to use it is Delicious Library. If you follow that to its logical conclusion, everything should be barcode-enabled, by Web-enabling it.
Monday, 21 August 2006There have been some interesting developments in Web caching lately, from a performance perspective; event loops are becoming mainstream, and there are lots of new contenders on the scene.
Friday, 18 August 2006Many thanks to J.J. Solari for translating the Caching Tutorial to French!
Monday, 14 August 2006Timbl has this great term “ Webizing” that he uses to talk about giving existing systems the benefits of the Web architecture. Despite the first part of “Web 2.0”, I think AJAX is in severe need of some serious Webizing.
Friday, 30 June 2006If you boil down the BNF in both RFC2396 and RFC3986, path segments can contain the following characters without percent-encoding them:
Saturday, 24 June 2006Hugo has finally blogged the big news. He’s left one of the coolest jobs in the world — working for the W3C — to come to another one of ‘em, working for Yahoo. I’m really looking forward to continuing to work with him; there’s lots to do!
Thursday, 22 June 2006Recently, there’s been a resurgence for the Link element in HTML; everything from Microformats to Atom autodiscovery is using it. This isn’t surprising; as machines start processing Web documents more, it’s necessary to use hyperlinks — the foundation of the Web — to tie resources together, without getting in users’ faces.
Tuesday, 20 June 2006A friend (who shall remain anonymous) pointed me to Microsoft’s announcement today regarding their foray into robotics, of all things. My eyes glazed over until they rested upon the Microsoft Robotics Application Model;
Friday, 9 June 2006See if your aggregator can subscribe to this feed (username/password: test/test) and post the results in comments.
Thursday, 25 May 2006When I joined Yahoo, one of the biggest adjustments I had to make was to their use of “Web Services”. There, that phrase means any kind of machine-to-machine communication using HTTP; SOAP isn’t assumed (or preferred).
Tuesday, 16 May 2006I just finished my XTech presentation, “ Web 2.0 on Speed”. here are the slides [pdf]; I’m going to try to s5 them soon. There isn’t much new in this talk; it’s just a synthesis of a few different observations;
Thursday, 11 May 2006Yaron publicly says what he’s doing at Microsoft (scroll down);
Wednesday, 10 May 2006Anne-Thomas Manes extolls the virtues of WS-*;
Sunday, 23 April 2006It’s official; I’ve got a last-minute slot at XTech, talking about all things Web caching.
Thursday, 20 April 2006Back at the W3C Technical Plenary, I argued that Working Groups need to concentrate on making more Web-friendly specifications. Here’s an example of one such lapse causing security problems on today’s Web.
Thursday, 13 April 2006I’ve had a lyric running through my head for the last day or so, thanks to a couple of bugs.
Friday, 7 April 2006It’s become axiomatic in some circles — especially in WS-* land, as well as in many other uses of XML — that the preferred (or only) means of offering extensibility is through URI-based namespaces, along with a flag to tell consumers when an extension needs to be understood (a.k.a. mustUnderstand).
Thursday, 6 April 2006I’m a little confused by Mark Baker’s stance regarding SOAP; he seems to encourage the Web services world to use SOAP on top of HTTP in a fashion compatible with HTTP.
Monday, 20 March 2006True to form, Don’s using his witty charm and good looks (such as they are ;) to shape discussion of a topic… in this case, REST, where he splits the RESTifarian world into two; “hi” and “lo.”
Thursday, 16 March 2006There’s some excitement out there about “ Cookie-less HTTP Authentication.”
Wednesday, 15 March 2006Microsoft and friends (of the keep your enemy closer variety, I suspect) have submitted WS-Transfer to the W3C. I found the Team comment interesting; e.g.,
Wednesday, 1 March 2006Over the weekend, I submitted a new draft of Feed History.
Saturday, 18 February 2006Have you ever posted a comment to a blog, found it missing, so you re-posted it, only to find two entries? Annoying, huh?
Tuesday, 7 February 2006Interesting; there are not one but two sessions at the upcoming ETech about taking Web applications offline.
Monday, 23 January 2006I’ve been playing around with some ideas that use XMLHttpRequest recently, but I keep on bumping up against implementation inconsistencies on IE vs. Safari vs. Opera vs. Mozilla. Although the interface exposed is pretty much the same, what it does in the background is very different, especially with regards to HTTP.
Wednesday, 11 January 2006It took two years, but Apple has finally taken steps to limit Safari’s content-sniffing ways;
Monday, 9 January 2006On the heels of mod_cgi, PHP now does the right thing (at least in 5.1) when setting the Allow header. mod_dav is still broken, though.
Saturday, 24 December 2005The useful end of RFC 3864 (at least regarding HTTP) is finally* here. When you need to know where a particular header is defined there’s now one place to do it; IANA’s Message header registry and repository have been filled with HTTP-related headers by RFC 4229.
Saturday, 26 November 2005The first in an occasional series about the real-world benefits of REST and the Web architecture, as applied to HTTP.
Monday, 7 November 2005More and more people are getting turned on to the advantages of using REST as a higher-level abstraction for networked applications, often comparing it favourably to SOAP and Web services.
Wednesday, 26 October 2005Does anybody know of a program or service that will look at a calendar file (e.g., vCalendar, iCalendar, hCalendar) and publish the entries on it as an RSS feed, where each entry in the feed has a link to that one calendar entry?
Sunday, 23 October 2005I don’t know if this has already been done (it’s not exactly rocket science), but for the benefit of those who want to emulate the W3C’s cool ,tools functions with mod_rewrite;
Saturday, 22 October 2005Why is it that Web browsers — Amaya excluded — don’t support PUT and DELETE? After all, if there are enough VCs foolish enough to part with their money for something like Flock, surely we could at least support all of HTTP’s methods.
Wednesday, 19 October 2005Roy Fielding has just closed a bug that’s been around since 1996, and which I’ve previously lamented here;
Wednesday, 5 October 2005Does anybody else chortle quietly when they see “2.0-this” and “2.0-that”?
Monday, 5 September 2005Feed History draft -04 is out, with the only major change being the replacement of fh:stateful with fh:incremental, with corresponding changes throughout the document, to make the concepts a bit clearer.
Thursday, 1 September 2005I took a pass at a revision of the RSS Tutorial for Content Publishers and Webmasters on the train this morning, as I realised it was dreadfully out of date.
Monday, 15 August 2005I’ve had a few e-mails asking how I got this site’s RSS feed to include its history, so here are the instructions for doing it in Moveable Type (the software that I use to manage this site). If you have instructions for other feed-generating software, please either leave them in comments below, or send me an e-mail.
Monday, 15 August 2005Draft -03 of Feed History: Enabling Stateful Syndication is now available. Significant changes include:
Saturday, 13 August 2005When I worked in the financial industry, I quickly noticed that Excel spreadsheets contain the bulk of the data in the enterprise. It may make IT execs tear their hair out, but having the data nearby and ready for analysis is sloppy, but oh-so-effective. The challenge is to make the data reusable elsewhere.
Wednesday, 10 August 2005For some time, I’ve noticed that people defining XML formats spend an inordinate amount of time talking about the structure of the format. This is especially apparent in standards working groups, where hours — no, days — can be spent agonizing over whether to make something an attribute or an element.
Monday, 8 August 2005Some folks at IONA have written a paper entitled Where HTTP Fails SOAP. I had a chance to look at this before I got it published, and their conclusions make a lot of sense — if you accept the premise that SOAP (and Web services) is about integration with existing applications.
Saturday, 16 July 2005After more than five years, syndication is maturing rapidly. It’s being used for more than blogging — whether it be stock quotes, system logs, or order lists — and even blogging will change in nature as it gets more popular; people will be using blogs to fundamentally change the way they do business, inside and outside the firewall.
Friday, 15 July 2005It’s been covered before elsewhere, but just a friendly reminder: ‘feed’ URIs are bad for the Web, as are any that are used solely for dispatch (e.g., ‘itms’, ‘ pcast’).
Saturday, 9 July 2005While a lot of companies are exploring blogs as a means of building communities, Intuit* (makers of Quicken, TurboTax, etc.) has skipped directly to the next logical step; using Wikis.
Friday, 8 July 2005You can describe just about anything with sufficient precision in plain English, given enough words. In practice, this doesn’t happen; specialised fields — whether science, finance or art — develop specialised jargon as a shorthand for concepts that are well-understood in that field. It gives greater precision, easier flow of ideas, and yes, it raises the bar to entry for newcomers.
Tuesday, 24 May 2005The W3C has just started a mailing list for discussion of Web description formats;
Sunday, 22 May 2005There’s been quite a kerfuffle over Google’s Web Accelerator, because it prefetches Web content.
Wednesday, 18 May 2005Marc Hadley has released WADL in the wild, and I’m intrigued; based on a first look, I’d say it’s the most promising Web (as opposed to Web Services) description language yet.
Thursday, 12 May 2005I happened to look at the HTTP headers returned from Google News just now (what can I say, I’m a HTTP geek), and I noticed something unusual;
Monday, 9 May 2005There’s a lot of cool apps emerging for GreaseMonkey (and GreaseMonkIE and PithHelmet, for IE and Safari respectively). It seems like these extensions have a love/hate relationship with the Web, philosophically.
Friday, 29 April 2005A while back, I published a series of entries ( 1, 2, 3, 4) about would-be Web Description Formats, with the intent of figuring out which (if any) is suitable, or whether a new one is required.
Sunday, 24 April 2005Should cookies be shared between your RSS aggregator and your Web browser? If they were, sites would be able to automatically personalise the feeds you subscribe to; would people be interested in that, or see it as an intrusion in their privacy?
Sunday, 3 April 2005Web metadata discovery is not a new topic, and one on which the final word has not been spoken. However, one of the most basic means of discovering something about a resource, the HTTP OPTIONS method, is not widely enabled by current implementations.
Monday, 21 March 2005A while back, I wrote up a description of a pattern for avoiding messages like “ click submit only once.” I didn’t do much after that, because I’ve been a bit busy, and because I wanted to do some implementation of a more general HTTP framework before I wrote a more formal document.
Tuesday, 22 February 2005I love the XSLT document function. With it, you can access the whole Web from a stylesheet; this gives a lot of flexibility, in the right situation.
Monday, 7 February 2005Werner makes an excellent point;
Wednesday, 19 January 2005More than a year after my modest suggestion, Google takes a step to fix comment spam. Hopefully, other people who re-publish Web content (like mailing list archives) will start doing this as well.
Friday, 17 December 2004The Australian Bureau of Statistics has released a very cool SVG-based animated population pyramid ( non-SVG preview) that very nicely visualises the change in that country’s population over time. While the pyramid technique is fairly common, the addition of a fourth dimension — time — and the ability to track a cohort through it really brings the data to life. Try the “highlight surplus of males or females” feature to see when you’ve got the least competition.
Wednesday, 15 December 2004I’m thinking about whether it would be a good idea to have a media type for Python source files, call it “text/python.”
Sunday, 10 October 2004In a recent post, Don gave his take on the enlightening nature of WS-Transfer;
Monday, 27 September 2004I was very interested to see the reaction to WS-Transfer [PDF] over the last few days. While the SOAP Resource Representation Header had opprobrium heaped upon it (see previous discussion), Transfer passed by with nothing more than a few nodding heads and people saying “aha.”
Wednesday, 8 September 2004Ever wonder where the heck a particular HTTP header is defined?
Saturday, 31 July 2004A few days ago I blogged a straw-man API for client-side HTTP based on dictionaries. This turns out to be well-aligned with a project I’ve had on the back burner for a while; coming up with some Python APIs for HTTP that are usable, encourage good practice, and well-aligned with the specifications.
Monday, 26 July 2004From the Daily Python URL comes another noteworthy API for XML; XMLFragment. I haven’t tried it yet (it doesn’t appear to be separately available, hint, hint), but I like the look of it.
Sunday, 18 July 2004Timbl has talked about Web-izing databasesand languages; what about operating systems? Despite Microsoft’s legal troubles brought about trying to integrate the browser into Windows, it’s a good idea.
Thursday, 1 July 2004When Tim O’Reilly gave his keynote at eWorld this year, one of his major points was that Internet-based mapping (e.g., Yahoo maps, Mapquest) had failed to take off, despite their obvious utility, because they were walled gardens; unlike eBay and Amazon, they don’t integrate user data and third-party applications very well.
Wednesday, 16 June 2004Check out the W eb H ypertext A pplication T echnology Working Group; it looks like our last, best hope for extending the browser platform to grow the Web.
Monday, 14 June 2004One thing about Web description formats that hasn’t seen much discussion yet is how people intend to use them.
Saturday, 5 June 2004Because Web sites often don’t make information available to us in the way we’d like, we have to bring the mountain to Mohammed and scrape screens.
Sunday, 30 May 2004Tim Bray is trying out “purple number signs” on his Web site to make fragment identifiers ubiquitous and easy to find.
Monday, 3 May 2004It looks like the HTTP PATCH method proposal might be based on Delta Encoding, which is IMO one of the cooler and lesser-known HTTP technologies.
Tuesday, 27 April 2004In the past, I’ve talked about reusing WSDL as a format for describing Web resources, as well as coming up with a bespoke format.
Monday, 19 April 2004One of the things that people find compelling about Web services is its promise of asynchrony. “HTTP is only request/response, and therefore synchronous; it’s terrible for long-lived business processes, where the server needs to contact the client at some arbitrary time in the future” they say.
Friday, 16 April 2004To use WSDL to describe RESTful interactions, you need some way of accommodating generative resource identifiers. In a nutshell, this means some part of the URI is dynamic. For example, with HTTP I might describe an address book where someone named “Jones” has a corresponding entry URI;
Sunday, 28 March 2004Ian Hickson is thinking about client-side technologies (scroll down a bit). Some of his ideas resonated;
Wednesday, 17 March 2004In an otherwise excellent article, Jon Udell blames the lack of one-click subscribe in syndication formats on lack of vision;
Sunday, 15 February 2004I’ve published a revision of the Caching Tutorial for Web Authors and Webmasters, the first non-trivial edit in some time almost since I wrote it in 1998. That said, there aren’t any substantial changes; this is mostly tweaking and incorporation of new information.
Tuesday, 3 February 2004Just got some mail regarding the Cacheability Engine which led me to NetKernel;
Monday, 8 December 2003HTTP provides considerable benefits to Web applications that take advantage of it; everything from scalability (through caching), client-integrated authentication, automated redirection, multiple format support and lots more.
Sunday, 7 December 2003Adam asks if there’s a description format for REST. I don’t know of any that have wide acceptance (and I think the hard-core RESTafarians will answer “REST is self-describing, that’s the point” ;) but I have been noodling on something for my own purposes.
Saturday, 13 September 2003I shudder when I see these words. Everyone I’ve asked has, at least once, gotten two orders of something online (personally, I’ve had the SonyEricsson store ship three duplicate orders); “Click Submit Only Once” is intended to stop that. The problem is, it puts me and every other shopper between a rock and a hard place.
Thursday, 21 August 2003I’ve heard several people in the industry assert that HTTP fundamentally limits the performance of applications that use it; in other words, there’s a considerable disadvantage to using it, and that therefore other protocols (usually proprietary or platform-specific systems that those same people happen to sell) are needed to “unleash the power of Web services.”
Monday, 11 August 2003I just found a draft finding that the W3C TAG published about a month ago, regarding the use of metadata in URIs. This is very cool, and I especially like the emphasis on authorities’ ability to embed metadata in URIs.
Monday, 4 August 2003Marc Hadley points out that the version of iDisk in OSX Panther looks like it will enable offline functionality with caching; it also looks to do some synchronization.
Tuesday, 29 July 2003Ted Leung points out that caching PUT (and other WebDAV methods) would suit Subversion - probably the most interesting WebDAV application under open development - quite well. The only thing he says that I disagree with (and it might just be a misunderstanding) is in regard to a need for a Subversion-specific client cache; the whole point of doing this with Web protocols it to avoid application-specific infrastructure. A well-designed WebDAV cache should work equally well for any application, not just Subversion.
Tuesday, 29 July 2003Mark Baker is the latest in a series to weigh in on the TAG issue regarding what a HTTP URI can identify.
Saturday, 26 July 2003If we WebDAV-enable Web applications, people will be able to interact with them like filesystems. To blog something, you’d be able to write an entry in the text editor of your choice, and then drag-and-drop them into what MSFT has called “Web folders.”
Saturday, 26 July 2003One of my personal background tasks in the last couple of months has been finding sample applications to excercise Tarawa with. Although my load is high and I’ve only got a single processor - me - I’m still trying to push this.
Friday, 25 July 2003Mark Pilgrim is starting to think about issues surrounding the transport, transfer and general moving around of the Format Formerly Known as Echo (nee Pie).
Saturday, 28 June 2003I feel compelled to respond to Norm Walsh’s thoughts on caching.
Tuesday, 17 June 2003What does this interesting new, ad hoc work have to do with this interesting , new standards work and this interesting, new-ish effort by GK?
Thursday, 12 June 2003Having a network-enabled (even if only through BlueTooth and infrared) is a heady experience; the ability to access the Web and sync applications from anywhere - really anywhere - is quite liberating.
Thursday, 29 May 2003Jonathan Rosenberg published a new Internet-Draft, XCAP, to the SIMPLE Working Group in the IETF. Here’s the skinny:
Thursday, 8 May 2003I know at least one person who will think that this is a good idea. Anybody else? I’d looove to do this work…
Monday, 5 May 2003I’ve finally gotten sick enough of a project that I’ve been working on for waaaay too long to release it to the unsuspecting^H^H^H general public.
Saturday, 26 April 2003For those who have been helping, it’s alive, has been for almost a week, but I still want to do a bit more documentation, hunt down a few bugs, and get some more unit tests down.
Thursday, 24 April 2003It’s not necessary to lament the lack of ETags on generated Web pages; cgi_buffer automagically generates and validates them for Perl, Python and PHP scripts.
Tuesday, 8 April 2003LiveHTTPHeaders for Mozilla is the best HTTP header sniffer I’ve seen yet; up till now, I’ve been using WebTee, but for most purposes, this is much better. Enjoy.
Thursday, 27 March 2003Dave seems excited by Macromedia’s announcement.
Tuesday, 25 March 2003Jorgen hits a subject that’s of great interest to me; RSS standardization. I originally started the Syndication list to get RSS moving towards some sort of recognized standard; more recently, my effort to register an RSS media type was stalled by the lack of a stable spec published by a recognized group.
Sunday, 26 January 2003I always wondered why so many people had their blogs’ comments and even trackback indicators turned off. Go ahead and surf around; it’s a rare blog indeed, at least in my experience, that has these features visible for the world to see.
Wednesday, 27 November 2002I’m extremely wary about the new prefetching feature in Mozilla. The Web caching community has tried this from about every angle, but the general consensus of professionals (with one notable exception) is that prefetching is a bad approach.