[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: KHTML blocking GUI [Was: Re: SMTP problems with KDE Mail & KNode]
From:       Lars Knoll <lars () trolltech ! com>
Date:       2002-01-31 12:51:03
[Download RAW message or body]


> On Thursday 31 January 2002 12:51, Dirk Mueller wrote:
> > which version are you talking about ?
>
> CVS HEAD from one or two weeks ago. Given the impressive KHTML speedups I
> have at home I guess that my KMail will seriously benefit from it here at
> work when I update CVS. But I am not that sure if it will completely fix
> all problems, especially for mails over 500 kb (system logs sometimes grow
> that big if e.g. packet logging is turned on). Hence the question here.
>
> > khtml does not interrupt the processing. it will process the part you
> > write() to it, and then return. thats it.
> >
> > if you write 50MB to it, well you'll be blocked for a while then, but
> > thats your choice.
>
> Then KMail should be change to send data in chunks to KHTML ;-)
>
> I CC-ed kfm-devel after some private mails with Michael, because opening
> large mails is blocking the GUI for a noticeable time. And from his
> responses I got the impression that it is KHTML's job to not block.
>
> So now I am confused... who should avoid the blocking? KMail or KHTML?

khtml expects the data to be delivered in chunks that are manageable. If you 
send 500k in one chunk it'll block, as it parses all 500k at once. One could 
work around that in khtml, but I'm not sure if that's really what we want. 
There is no problem in konqueror, as kio sends its data in 32k chunks.

Lars

[prev in list] [next in list] [prev in thread] [next in thread]