Bug 40323 - KIO slaves should have a way to specify a max chunk size for readData(), otherwise progress bar isn't updated often enough with slow slaves
Summary: KIO slaves should have a way to specify a max chunk size for readData(), othe...
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: kioslave (show other bugs)
Version: unspecified
Platform: unspecified Other
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-06 21:18 UTC by germain
Modified: 2018-04-16 18:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description germain 2002-04-06 21:11:49 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           
Version:           
Severity:          wishlist
Installed from:    
Compiler:          
OS:                
OS/Compiler notes: 

In the current implementation sent chunks in readData() have an unpredictable size.

This can be quite un-handy if your slave :
a) is slow 
b) uses a different chunk size

I had both cases with a slave communicating with a serial device:
- it has 8 Kb/sec throughput but konqui send 32 to 64 kb chunks => progress bar is updated every 4 or 8 seconds !
- I had to add some setRawData() to split those large chunks into 4Kb chunks which is not very clean

So wouldn't it be possible to add an extra parameter to readData() for instance:
readData( QByteArray & data int length=-1 )?

Or any other way to emit a recommendation for chunk sizes ?


(Submitted via bugs.kde.org)
Comment 1 Nate Graham 2018-04-16 18:43:15 UTC
Doesn't seem to be a problem in KDE Frameworks 5.45.