--nextPart3108277.LeWZeHm3vI
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

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

> What was surprising here is that the above solution can be implemented ve=
ry
> 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=
=2E=20
starting things with some (printable, ASCII) special character like space, =
#=20
or whatever. That way we can avoid that a server can inject such things int=
o=20
the metadata cache. Otherwise you would have to filter out any metadata fro=
m=20
the server that starts with _kio_internal to make sure it doesn't try to fo=
ol=20
us into something.

Eike

--nextPart3108277.LeWZeHm3vI
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEABECAAYFAkvYWwoACgkQXKSJPmm5/E6H4wCfXSc2R19VmwJXhQWp0AjiIACc
jR0An1AH46cMyRm3Hk9Gb/OHpUdiBp8h
=S7xn
-----END PGP SIGNATURE-----

--nextPart3108277.LeWZeHm3vI--