CompuServe Messages

Yah, well, I'm sure even with a 28.8k connection the Web will be slow. If CIS at least supported compression things might be a little better. And AMosaic could be a *lot* better. It should be able to download pages to one's local computer and have them be *useable* and only updated if the real page has changed. I downloaded a 1/2MB gopher tree over at the Library of Congress before I knew about he cancel button, and there was no size indication anyway, and it was *USELESS*! Except as a reference, but I couldn't seem to load it into AMosaic and click on a document and then jump there. I'm definitely going to set a different default site for AMosaic, because I timed it today for the AMosaic home page and it took 1:30 to get the first page. I'll upload the Hotlist now. >>"What can't the whole page be transmitted at once?" The HTTP protocol doesn't let you do it.<< If the protocol was more sophisticated, it could process everything quickly even with dependant sends, like based on graphic size thresholds and cached graphics and so on. It sounds to me like HTTP is VERY dumb. The big delays for me are much more from waiting for connections rather than transfers. And some links seem like you have to get the graphic first–there aren't always those little arrows above the inlined graphic icon. I did find gopher support, although there are a lot of pages–gopher and otherwise–that seem to be down. They refuse access. And then some of them seem to time out. The big problem seems to be that they're putting more eye-candy into the web than the web can handle–when you consider that the vast majority of web surfers must be using serial connections. I'm sure the web is a marvel when you're hooked up directly to a backbone, although I imagine that connection requests can be almost as slow–isn't most of the time waiting for a connection spent while the server processes the request, or is most of it spent waiting for the request to travel? Anyway, thanks for your time and thoughts. Mr. Zombie