May I ask why you think this is a good thing?
Maybe the data which would be served via http is already in AFS (for
ease of administration/updates, since http is a read-only protocol).
Access control in AFS is here *RIGHT NOW*; http won't have it for a
while now.
AFS can be replicated, avoiding single points of failure, while http
doesn't allow for this in current practice.
If I read the source correctly (and feel free to correct me here if
I'm wrong) httpd forks at least once per file transferred, putting
gratuitous extra load on the file server, while AFS doesn't.
AFS has a local cache which actually seems to work; mosaic doesn't; if
I want to go back to a page I've seen recently, mosaic has to go back
and fetch it again over the network.
I don't know if Ted T'so <[EMAIL PROTECTED]> is reading this, but he
mentioned to me that he recently added a general "bypass" hack to
Mosaic and got something like a 4x or 5x boost in (cold AFS cache)
Mosaic performance for some complicated home pages.
- Bill
