public inbox for mlmmj@mlmmj.org
 help / color / mirror / Atom feed
From: Moritz Wilhelmy <ml+mmj@wzff.de>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Google Summer of Code
Date: Sun, 06 Mar 2011 16:31:50 +0000	[thread overview]
Message-ID: <20110306163150.GF10635@barfooze.de> (raw)
In-Reply-To: <AANLkTi=N6TUvhAPjxrR=iR3gJc_LQXCXR+kxSUqPL_bp@mail.gmail.com>

Hi,

On Sun, Mar 06, 2011 at 11:32:09PM +0800, Thomas Goirand wrote:
> IMHO, using C for writing web interfaces is both counter-productive and
> a security risk. 

Not really any more than writing an MLM in C...
IMHO, C is perfectly fine, as long as the programmers know what they're doing.
A not-insignificant part of your operating system is written in C, and you
don't consider that a security risk, do you?

> BTW, what is the problem with things like mhonarc? I think that generating
> static content is always better than (uselessly) generating on-the-fly
> dynamic content.

Just a thought, maybe search-queries against the list? (Although this can also
be done by external search engines if your list is in the index, but maybe you
don't want this, for instance for private lists? Sure, you could just download
the archive as mbox file, and use grep or mairix or mutt -f listarchive...)

> If we need a db, *please* make it possible to choose the back-end (like
> for example: sqlite, postgres or MySQL).

Maybe externalise this, so mlmmj uses a separate mlmmj-user program to check
against a db, filesystem or other ways of data storage?
I'd still prefer not to use a DB at all. The idea that everything needs to be 
backed by a full-fledged database with access control and whatever is a common
mistake in computing. For something as simple as mlmmj, UNIX permissions should
suffice. I agree that some people might want to integrate mlmmj into their
existing, db-backed projects, though.

Best regards,

Moritz


  parent reply	other threads:[~2011-03-06 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03 20:40 [mlmmj] Google Summer of Code Wolf Bergenheim
2011-03-04  3:47 ` Marcelo
2011-03-04  3:48 ` Marcelo
2011-03-04 13:14 ` Mark Alan
2011-03-04 13:38 ` Christoph Thiel
2011-03-04 14:22 ` Thomas Goirand
2011-03-04 15:13 ` Christoph Thiel
2011-03-04 22:45 ` Wolf Bergenheim
2011-03-05  1:01 ` Marcelo
2011-03-06 12:29 ` Ben Schmidt
2011-03-06 15:32 ` Thomas Goirand
2011-03-06 16:31 ` Moritz Wilhelmy [this message]
2011-03-07  8:18 ` Thomas Goirand
2011-03-07 10:07 ` Ben Schmidt

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=20110306163150.GF10635@barfooze.de \
    --to=ml+mmj@wzff.de \
    --cc=mlmmj@mlmmj.org \
    /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