KIO::NetAccess static methods question

[Rafael Fernández López]

Hi,

> ... and in that situation you can just create the job with the KIO::foo()
> API and call NetAccess::synchronousRun() or job->exec().
> For this reason, many NetAccess calls have been deprecated, and IMHO
> even more should be. There's no point in duplicating the entire Job API
> again in NetAccess, when we can just use the Job API in the first place,
> in combination with synchronousRun or exec.
> The only thing in NetAccess that still makes sense, apart from
> synchronousRun, is download+removeTempFile since this takes care of the
> tempfile handling, and exists() because it's easier to use than stat. But
> in those cases the idea was: not providing a way to hide the progress
> dialog because it only shows up after a few seconds anyway, i.e. when the
> operation is starting to take too long, and in those cases we do want to
> show a progress dialog -- remember that the application is not responding
> while it's stuck in NetAccess...

Well, I get your point but we could agree that we have this "easier interface 
and shorter for the final end developer" almost for free and we can use it.

From my point of view, this simplifies the way things would be done the other 
ways you explained.

As a result, should I work on this or not ? :)


-- 
Rafael Fernández López

GPG Fingerprint: B9F4 4730 43F8 FFDD CC5E BA8E 724E 406E 3F01 D070
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071022/dc777836/attachment.sig>