Stephen McConnell asked:
> File system - a convenient and simple solution - but should a file
> system driven approach be the basis for the next generation?
The basis is a URI space. Whether a URI is efficiently served by a static
file, or by some servlet, CGI or Grandma Moses typing very VERY fast really
should not be visible to the user-agent.
> A solution must be implementation independent
The URI is a request for content. It should not change, regardless of the
means by which the content is generated.
> So why a preoccupation with meta-less file system structures as opposed
> to a preoccupation with an extensible repository protocol?
The "extensible repository protocol" is HTTP. Nothing else needs to be
visible. The only thing that the infrastructure team needs to deal with is
the implementation of the URI space (allowing that the content addressed by
a URI can vary based upon the user-agent).