On Wed, 05 Nov 2008 11:45:08 GMT Richard Porter <[EMAIL PROTECTED]> wrote:
> > You are attempting to use a cooperatively multitasked operating > > system to both serve and display content, expect such problems even > > if the browser is working acceptibly with external servers. > > The problem seems to be that NetSurf isn't cooperating because it's > spending all its time clocking up the time and not releasing control > to any oter task. But is this really the case? What about all the > other processes that need to run if an object is requested and > received from a remote server? Are they all interrupt-driven? NetSurf's internal model of releasing CPU time to the OS is... complex. We'd like to fix that, but it's pretty low on the to do list. Most RISC OS server software either runs as a module (and thus can continue even when the WIMP is blocked) or suggest you don't use the machine for anything else while the server software is running. Given RISC OS's architecture, serving stuff from RISC OS is likely to be a pain. > Why should this occur when NS is requesting a style sheet and not > when it's requesting an image? Other browsers can cooperate with > WebJames so NS should be able to. NetSurf working with WebJames on the same machine working at all is already a miracle. We spent many hours trying to discover the cause of the deadlock, but to no avail. I seem to recall we pointed the finger of blame at the RISC OS networking stack, as well as the co-operative multi-tasking. There's no reason it /should/ be blocking, but does it. Perhaps now the sources the the IP stack are available, somebody might spend some time making it less dreadful.
