atom feed18 messages in org.kde.kde-core-develRe: [PATCH] DNS cache for Konqueror/KIO
FromSent OnAttachments
Roland HarnauJun 22, 2008 6:23 am.diff
Andreas HartmetzJun 22, 2008 6:32 pm 
Thiago MacieiraJun 22, 2008 11:35 pm 
Allan Sandfeld JensenJun 23, 2008 1:34 am 
Richard MooreJun 23, 2008 7:37 am 
Thiago MacieiraJun 23, 2008 8:10 am 
Roland HarnauJun 25, 2008 11:03 am.patch
Roland HarnauJun 25, 2008 11:04 am 
David FaureJun 25, 2008 1:32 pm 
Andreas HartmetzJun 27, 2008 12:14 pm 
Thiago MacieiraJul 1, 2008 4:02 pm 
Thiago MacieiraJul 1, 2008 4:48 pm 
Roland HarnauJul 7, 2008 7:30 am.patch
Thiago MacieiraJul 7, 2008 7:57 am 
David FaureJul 7, 2008 3:59 pm 
Thiago MacieiraJul 7, 2008 7:13 pm 
Roland HarnauJul 9, 2008 1:08 pm 
Thiago MacieiraJul 9, 2008 1:42 pm 
Subject:Re: [PATCH] DNS cache for Konqueror/KIO
From:Roland Harnau (trut@googlemail.com)
Date:Jun 25, 2008 11:04:02 am
List:org.kde.kde-core-devel

2008/6/23, Andreas Hartmetz <ahar@gmail.com>:

Did you consider making the name cache even more central like kded or kdeinit? That should give us more cache hits in some cases.

My first try to integrate the resolver into KIO was via a standalone DBus
service, i.e. I wrote a DBus adapter with "delayed reply". The result was
completely disappointing because of high latency. Besides, I doubt the session
bus is apt to handle the slave storm usually triggered by Konqueror. So I think
a kded module is out of the question. The location in the application's address
space is of course not forced, but allows fast name resolution without much
additional complexity.