NetAccess::statInternal and showing job progress

Aaron J. Seigo aseigo at
Sat Jul 17 02:57:51 BST 2010

On July 16, 2010, you wrote:
> On Friday 16 July 2010 20:42:48 Aaron J. Seigo wrote:
> > [...] just to show what is, imho, fairly uninteresting information [...]
> It will become interesting when the server does not respond in "expected"
> time. Then you can see where it is blocking, what server, and eventually
> what location it tries to access.

i don't think this is best achieved through a notification (since it 
"penalizes" the user for every success in case of failure), nor are apps that 
are likely to use KIO::NetAccess (a synchronous API) likely to care or be 
equipped to do this. 

i agree with the intention you note, but disagree that this particular area of 
KIO's code is relevant to that intention :)

Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list