[PATCH] Request for adding internal meta-data support to KIO...

Rolf Eike Beer kde at opensource.sf-tec.de
Wed Apr 28 16:57:57 BST 2010

Am Mittwoch 28 April 2010 07:06:35 schrieb Dawit A:

> What was surprising here is that the above solution can be implemented very
> easily. With only one additional requirement to qualify meta-data as
> internal, we can use the existing method that ioslaves use to send
> meta-data back to applications to solve the issue. What is this
> requirement ? We simply state/assume that a meta-data whose key starts
> with the keyword
> "_kio_internal_" will be treated as an internal meta-data and handled
> separately from the regular meta-data container that holds values slated to
> be sent to applications. You can read the details of how this is supposed
> to work by either reading the attached patch or simply reading the changes
> I made to the DESIGN.metadata document which is included with the patch.

I suggest using something that must not be a valid metadata identifier. E.g. 
starting things with some (printable, ASCII) special character like space, # 
or whatever. That way we can avoid that a server can inject such things into 
the metadata cache. Otherwise you would have to filter out any metadata from 
the server that starts with _kio_internal to make sure it doesn't try to fool 
us into something.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100428/458683bd/attachment.sig>

More information about the kde-core-devel mailing list