Bug 164015

Summary:	Rewrite kio_zip with fuse-zip backend
Product:	[Unmaintained] kio	Reporter:	Alexander Galanin <al-kde-bugs>
Component:	zip	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	finex, nate
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	fuse-zip, kio-zip and kio-krarc performance comparison

Description Alexander Galanin 2008-06-14 08:33:53 UTC

Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc (GCC) 4.2.3 (Debian 4.2.3-5) 
OS:                Linux

I want to suggest rewriting kio_zip slave with fuse-zip backend. fuse-zip if a FUSE file system for ZIP archivez with write support. You can download it at http://fuse-zip.googlecode.com. At this moment FUSE are present for linux 2.4.x, 2.6.x, FreeBSD, Solaris, Mac OS X. There are experimental implementations for Microsoft Windows platform.

With fuse-zip you can provide access to virtual file system to any application without needs to cimpile it with using KIO. As shown with tests(see attachment) fuse-zip are many times faster that kio_zip or kio_krarc.

With this enhancement you can resolve bugs 75324(partially), 125458, 82438(partially), 73821, 96629.

t is time to make an adequate response to the Gnome GVFS-FUSE bridge!

Comment 1 Alexander Galanin 2008-06-14 08:34:53 UTC

Created attachment 25324 [details]
fuse-zip, kio-zip and kio-krarc performance comparison

Comment 2 FiNeX 2008-06-14 10:44:02 UTC

Will implementing this add the possibility to write directly into a zip file like a "classic" folder too?

Comment 3 Alexander Galanin 2008-06-14 10:46:12 UTC

> Will implementing this add the possibility to write directly into a zip file like a "classic" folder too? 

Yes! You can test fuse-zip and make sure that you can transparently do anything with archive content: add/remove files, view/change content, make/remove directories...

Comment 4 Pino Toscano 2008-06-30 22:00:52 UTC

> Will implementing this add the possibility to write directly into a zip file like a "classic" folder too?

This is possible even with the current kioslave, as the KDE libraries already allow that.
What is missing is the "glue code", see bug 77127. Switching the code used for reading the zip's to another solution does not add this "glue" automatically, of course.

Comment 5 Alexander Galanin 2008-07-01 09:39:55 UTC

> Switching the code used for reading the zip's to another solution does not add this "glue" automatically, of course. 

With fuse-zip based implementation you can write to zip files with fopen()/fread()/fwrite() without any "glue" code.

Comment 6 David Faure 2008-07-01 11:32:57 UTC

You still need to implement the kioslave part of this :-)

Comment 7 Alexander Galanin 2008-07-01 11:58:47 UTC

> You still need to implement the kioslave part of this :-)

Yes, and it is content of my suggestion.

Comment 8 mic 2008-08-11 05:29:54 UTC

*** This bug has been confirmed by popular vote. ***

Comment 9 Nate Graham 2018-04-17 22:05:24 UTC

What's the relationship between this request and Bug 75324?

Comment 10 Andrew Crouthamel 2018-09-28 03:09:44 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 11 Nate Graham 2018-09-28 19:03:12 UTC


*** This bug has been marked as a duplicate of bug 75324 ***