From kde-core-devel Fri Apr 30 18:14:05 2010 From: Rolf Eike Beer Date: Fri, 30 Apr 2010 18:14:05 +0000 To: kde-core-devel Subject: Re: [PATCH] Request for adding internal meta-data support to KIO... Message-Id: <201004302014.05728.kde () opensource ! sf-tec ! de> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=127265127614525 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1342095.P50cl7v638" --nextPart1342095.P50cl7v638 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dawit A wrote: > On Thursday, April 29, 2010 02:14:45 Rolf Eike Beer wrote: > > My point is less a thing that this (or any other) slave will do or not > > with this data now or in one year. My point is that when this is some > > internal state of whatever kind than we should under no way allow remote > > systems to influence that in any way but through our code that does it > > explicitely. It's the same like you make class members private instead > > of making them public and hoping that noone will touch them if you name > > them > > _private_member_foo. >=20 > Again there is no way for a remote system to influence the meta-data > system, internal or otherwise, right now unless the developer of an > ioslave implicitly allows it to do so. As such I fail to see how you can > protect against that by using special characters in the keyword. If the > developer is going to expose it to influence by the remote system, what > stops him from simply adding the keyword directly ? To me it is simply a > pointless exercise since you cannot control what a developer will do in > the end. What you are saying would make a great deal of sense if we > automatically mapped meta-data sent by a remote system directly into our > internal scheme, but we do not do that. Ok, so if there is no way to put "global" entries in the metadata everythin= g=20 is fine. The HTTP ioslave e.g. puts everything in the Content-Disposition=20 header as Content-Disposition-foo in the metadata. If noone inserts un-pref= ixed=20 wildcard data in the metadata we're save. Eike --nextPart1342095.P50cl7v638 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) iEYEABECAAYFAkvbHe0ACgkQXKSJPmm5/E4UWwCgmgz4jCgf7d3o7YcD0jNgXKpT uSEAn1IFfI6+P4UZjsy0G28CI7LQKoVq =kpfa -----END PGP SIGNATURE----- --nextPart1342095.P50cl7v638--