| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next


Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

Consciousness From Max Entropy; Democrats; Harvard Will Fix Black Poverty; Modelling Bicycle Wheels; Amusing Polling Outlier; If Labour keeps telling working class people...; Populism and Choice; Books on Defeat; Enrique Ferrari - Argentine Author; Transcript of German Scientists on Learning of Hiroshima; Calvert Journal; Telephone System Quotes for Cat Soft LLC; Owen Jones on Twitter; Telephone System Quotes for Cat Soft LLC; Possible Japanese Authors; Complex American Literature; Chutney v5; Weird Componentized Virus; Interesting Argentinian Author - Antonio Di Benedetto; Useful Thread on MetaPhysics; RAND on fighting online anarchy (2001); Now Is Cat Soft LLC's Chance To Save Up To 32% On Mail; NSA Hacked; Call Center Services for Cat Soft LLC; Very Good LRB Article on Brexit; Nussbaum on Anger; Credit Card Processing for Cat Soft LLC; Discover new movies on demand in our online cinema; Tasting; Credit Card Processing for Cat Soft LLC; Apple + Kiwi Jam; Hit Me; Increase Efficiency with GPS Vehicle Tracking for Cat Soft LLC; Sudoku - CSP + Chaos; Recycling Electronics In Santiago; Vector Displays in OpenGL; Call Center Services for Cat Soft LLC; And Anti-Aliased; OpenGL - Render via Intermediate Texture; And Garmin Connect; Using Garmin Forerunner 230 With Linux; Payroll Service Quotes for Cat Soft LLC; (Beating Dead Horse) StackOverflow; Current State of Justice in China; Now Is Cat Soft LLC's Chance To Save Up To 32% On Mail; Axiom of Determinacy; Ewww; Fee Chaos Book; Course on Differential Geometry; Increase Efficiency with GPS Vehicle Tracking for Cat Soft LLC; Okay, but...; Sparse Matrices, Deep Learning; Sounds Bad; Applebaum Rape; Tomato Chutney v4; Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result; Your diamond is a beaten up mess; Maths Books; Good Bike Route from Providencia / Las Condes to Panul\; Iain Pears (Author of Complex Plots); Plum Jam; Excellent; More Recently; For a moment I forgot StackOverflow sucked; A Few Weeks On...; Chilean Book Recommendations; How To Write Shared Libraries; Jenny Erpenbeck (Author); Dijkstra, Coins, Tables; Python libraries error on OpenSuse; Deserving Trump; And Smugness; McCloskey Economics Trilogy; cmocka - Mocks for C; Concept Creep (Americans); Futhark - OpenCL Language; Moved / Gone; Fan and USB issues; Burgers in Santiago; The Origin of Icosahedral Symmetry in Viruses; autoenum on PyPI; Jars Explains; Tomato Chutney v3; REST; US Elections and Gender: 24 Point Swing; PPPoE on OpenSuse Leap 42.1; SuperMicro X10SDV-TLN4F/F with Opensuse Leap 42.1; Big Data AI Could Be Very Bad Indeed....; Cornering; Postcapitalism (Paul Mason); Black Science Fiction; Git is not a CDN; Mining of Massive Data Sets; Rachel Kaadzi Ghansah; How great republics meet their end; Raspberry, Strawberry and Banana Jam; Interesting Dead Areas of Math; Later Taste; For Sale

© 2006-2015 Andrew Cooke (site) / post authors (content).

Re: [Cute] URI names - nice argument

From: "andrew cooke" <andrew@...>

Date: Fri, 9 Dec 2005 09:12:24 -0300 (CLST)

And here's the reason why voi:// is used...


On 2005 Dec 8 , at 21.42, Doug Tody wrote:

> A given URI may resolve into multiple URLs pointing to multiple
> instances.

That's the difference!  I had completely forgotten about the one-to-
many resolution.

I'm working this through out loud here, Doug, for my benefit rather
than yours, as I imagine you've been through this already, and
because it might be useful (to me if noone else) to have the whole
argument in one place.

The underlying reason is that the resources in question are biggish.
This breaks the assumptions of the best practice/architecture
analysis in two independent ways:

1. The resources are replicated, and large enough that the client's
location on the network matters.

2. The size means that HTTP is probably not the best transport
mechanism, but instead GridFTP, or BitTorrent, or something else.

In both cases, the client can't be expected to make a good decision
about which source to use (because that will depend on details of the
national and intercontinental network, which will moreover change in
time), nor which protocol to use (which will also depend on network
environment and time).  A local resolver can be expected to know
these things, either by discovery or configuration.

The assumption that's broken is the single, almost hidden, assumption
that the transport issue is solved -- `use HTTP'.  Even if that were
sorted out, and everyone decided that GridFTP (say) was the single
best transport, the analysis also assumes that there is a single
source -- a single DNS host -- for the resource; the replication in
(1) means that we're not assuming that.  That can also be got around,
by having a DNS name be handled by multiple geographically dispersed
IP addresses (Google is well known to do this), but this is
technically complicated and therefore fragile, and also centralised.

Even if they acknowledge the first HTTP point, the response to this
second point on the part of the TAG (the W3C Technical Architecture
Group, authors of the Web Architecture document) would be to point at
the replication implicit in (1).  One of the good features of HTTP is
that it is stateless, which means that it is very friendly to caches
and proxies, so you _can_ have a simple single source, and just rely
on caches to speed things up -- don't try to outsmart the network!
But the sizes undermine that argument, too: few places have the
resources to cache lots of multi-GB files, and if regional or
national centres were set up which could handle that, it would
require configuration cleverness to use them.  Thus the replication
is essentially a type of preemptive caching.

On the other hand: I suppose there is still one case for using HTTP
with a (nominally) single source, along with a smart local proxy,
which spots when you're requesting a resource/source it knows about,
and satisfies those requests using (transparently) a separate network
of replicas and protocols.  That way, the client gets all the
simplicity, predictability and API advantages of using HTTP naively
(because that would work fine over a local network).  The proxy is
effectively acting as a resolver, but the client is interacting with
it using an extremely simple and possibly built-in protocol/API, and
so doesn't have to care.  Is there milage in that?

...but I think I'm going on at too much length now, so I'll shut up!

All the best,


compute mailing list

Comment on this post