Re: Another take on versioning

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeni Tennison writes:

> Now what happens? Of course developers update the pipeline libraries
> that their pipelines use, especially because they want some new
> pipelines that have been added, but not everyone updates their
> pipeline processor, mostly because they can't (because they're built
> in to the databases that they've paid vast sums of money for).
>
> Now:
>
>   (a) whenever those people run their pipelines, the processor has to
> make a connection to the W3C server to get hold of the v2
> declarations. On some websites, this is every time there's a request
> to the website. The people using the pipelines are largely oblivious
> to this fact, with the result that there are millions of hits per day
> on the W3C website requesting that pipeline library, amounting to a
> DDoS attack. One day, the W3C website is unreachable, effectively
> preventing thousands of other websites from working.
>
>   (b) developers on planes get extremely pissed off at not being able
> to run their pipelines at all just because they lack internet
> connectivity.

This is a good analysis, and the dependence on caching in principle
and connectivity in practice is indeed a serious flaw with the _status
quo_ use of p:import and fixed-URI-version-defining-libraries.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFK1EGlkjnJixAXWBoRAkOBAJ97zlBX98YmY9Zxmgy2p/FPLdSZewCeJwEv
VX/NMVpU0ZT2FDOND0VAkyQ=
=5zKC
-----END PGP SIGNATURE-----

Received on Tuesday, 13 October 2009 09:00:55 UTC