kio_giobridge IO slave

[Kevin Ottens]

Le vendredi 4 janvier 2008, Kevin Krammer a écrit :
> On Thursday 03 January 2008, Vlad Codrea wrote:
> > It links to glib and therefore introduces a compile-time dependency on
> > glib. This wastes memory because now KDE has two low-level frameworks
> > that have redundant functionality: QtCore and Glib.
>
> It is an IO slave, a separate helper process, so this is hardly a problem.
> Avoiding unnessesary dependencies for application libraries is one of the
> advantages of doing things out-of-process, isn't it?

Right, so it's not a library and best case it should be in kdebase/runtime... 
That said, I really see no reason to ship that with our desktop by default.

> > 4) There already are mature and tested KIO slaves to handle all the
> > protocols that GVFS handles, with less indirection and room for bugs.
>
> And, as I wrote above, they are still available and the default and one
> doesn't have to use the bridge slave. It just adds another option.
> That's what we have plugable backends for, don't we?

IMO it's a candidate for extragear then (or kdeaddons, or kdeutils). 
Definitely not kdelibs or kdebase.

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080104/a9362e47/attachment.sig>