Page is not reloaded in a KHTML part

Andras Mantia amantia at kde.org
Thu Mar 11 12:47:35 GMT 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 11 March 2004 13:46, you wrote:
> > If the above one is the reason of the problem, I think it makes sense to
> > use some flag and use the cache only if the file was completely loaded.
>
> No, I think the existing set of flags and variables is completely
> sufficient to determine whether the request is still running. Examine for
> example d->m_workingURL, d->m_bComplete, d->m_doc->parsing() and things
> like that.

I don't know the internals, but if you say those are enough, it's good. :-)

> Another option would be deleting the cache entry before the reload request.
> That can be done through a special command in KIO:
> 	KIO::http_update_cache(url, true, 0);

For an outsider, this looks a more elegant solution. If somebody request to 
reload a page the cache entry could be invalidated as anyway if the loading 
was completed the cache entry will be re-added. If the loading was 
interrupted, it doesn't make sense to use an old cache entry next time.

Andras

>
> Better Ideas, anyone?
>
> Cheers,
> Tobias

- -- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAUF/nTQdfac6L/08RAktOAJ9X7Pgt0PaW9pIIo4qnE1gYD9a/ugCfS02g
ntLvF+O4n2hH0vTfl8VUZVo=
=ShQd
-----END PGP SIGNATURE-----




More information about the kfm-devel mailing list