On Sat, 22 Jan 2000 22:45:54 +0100, Clarence Verge wrote:
> It's pretty easy to see here why testing should be done with a '386.
> A MAJOR portion of ALL times above is due to slow LOCAL processing.
> Arache version 1.6b1 STILL links client side images and verifies images
> TWICE on a re-load. Doing this once only would cut a whole MINUTE off
> off the above reload times for the Computer Products page.
> It seems to me that version 1.60b1 is SLOWER on local operations.
>
Perhaps someone could explain this to me. Why is it that other graphic
browsers (Opera is the other one I've used most) download a page AND
display it PROPERLY as it comes in, inserting graphics bit by bit as
they arrive?
I'm not ready for that glib "Oh - because it's Windoze" answer. At the
end of the day, windoze programmes are running code on a microprocessor
just like any other programmes. So if they can do it, so can Arachne -
if the code says so!
Clarence is right spot-on here - why does Arachne (any version from
about 1.44) waste so much time doing things more than once? If I
try and download a page that turns out to be, say, 120kB long (e.g.
some sort of stock list or index page), I sometimes wonder whether
Arachne is going to display it before Christmas....
This is definitely one fundamental problem that MUST be fixed
BEFORE any more bells & whistles come along - PLEASE!!!
Ron.
