From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: A change to string encoding
Date: Tue, 10 Mar 2009 11:58:38 -0400 [thread overview]
Message-ID: <200903101158.38990.sgrubb@redhat.com> (raw)
In-Reply-To: <1236683237.3386.22.camel@localhost.localdomain>
On Tuesday 10 March 2009 07:07:17 am Matthew Booth wrote:
> The problem with current string encoding is that it is parsable, but
> non-human readable.
There are times when it has things that would never be human readable.
> URL encoding is just one way to achieve this, and has the advantage of
> being widely implemented.
Inside the kernel?
> I'm sure this has been considered before. Given that it's a road I'm
> considering heading down, what were the reasons for not doing it?
Can you encode data structures in it? The kernel developer at the time wanted
something that was either already in the kernel or something that could be
implemented in a couple lines of code and something that works for any kind
of encoding that needed to be done. So, I think minimal amount of code and
maximum flexibility is what drove the decision.
-Steve
next prev parent reply other threads:[~2009-03-10 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 11:07 A change to string encoding Matthew Booth
2009-03-10 15:58 ` Steve Grubb [this message]
2009-03-10 18:13 ` Matthew Booth
2009-03-10 19:55 ` John Dennis
2009-03-10 16:22 ` Tomas Mraz
2009-03-10 18:51 ` Eric Paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903101158.38990.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox