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

List:       kde-devel
Subject:    Re: low performance of kio
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-04-21 19:10:11
[Download RAW message or body]

On Thu, Apr 20, 2000 at 02:06:29PM -0500, mosfet wrote:
> David Faure wrote:
> ..snip..
> > > Well, if you read my part of the thread I never mentioned copying once
> > > ;-)
> > 
> > No, but grep for 'copy' in the text above ;-)
> > I wasn't replying to you here :/
> > 
> 
> Again, as a non-KIO developer I'm clueless but wouldn't copy and move be
> bad examples of timing the data transfer between application and KIO
> slave? Shouldn't the slave itself be able to manage all the data
> transfer within it's own address space without sending the bits to the
> application? If that's the case I'm not concerned about that at all, and
> explains while Konq is pretty fast as far as copy and move is concerned.

void FileProtocol::copy( const QString &src, const QString &dest,
                         int _mode, bool _overwrite ) 

> But that does not address things like opening and saving documents where
> you do have to communicate between KIO's slaves and the application.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

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