🚀 go-pugleaf

Michael van Elst (mlelstv@serpens.rhein.de) writes:
>>>>You're right, it was because of Executive. I rebooted without it and
>>>>suddenly it started working the same as IBrowse, even following links
>>>>in part-loaded pages while the .html was still loading just like
>>>>IBrowse does. Unfortunately the whole machine became sluggish while it
>>>>was processing (boy, it's really easy to notice the difference when
>>>>you're not running Executive!).
>
>>>Well, that happens when you have to do calculations.
>
>>If AWeb put the image decoding at a lower priority itself (which is a
>>reasonable thing to do,
>
>That's something that you do not want. You want I/O, decoding and
>rendering done concurrently and this means: at the same priority so
>that they are timesliced.

  I don't think that would be a good idea. You don't want image decoding
  to slow down rendering or response to GUI events. The magic word here
  is: threads.

  The best way to implement a WWW browser would be to use threads with
  fixed priorities. Five threads would be needed with, for example, these
  priorities:

     5 user I/O
     4 transfer
     3 rendering
     2 decoder (small images)
     1 decoder (large images)

  You can implement this on Amiga, but it doesn't work with dynamic
  priorities. If we would have threads on Amiga, there would be only
  one task to be scheduled.

  And with this arrangement, small images would appear more quickly,
  not held back by one large image that takes ages to decode. The
  two decoder-threads could also have same priority.
-- 
                                      __
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~///~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       Petri Nordlund             __///         petrin@megabaud.fi
 ---------------------------------\XX/----------------------------------