From: Milan Zamazal <pdm@zamazal.org>
To: Peter Novodvorsky <nidd@altlinux.ru>
Cc: gnats-devel@sources.redhat.com
Subject: Re: modular database backends
Date: Mon, 28 May 2001 14:37:00 -0000 [thread overview]
Message-ID: <878zjhdvwu.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <7xr8xaac5q.fsf@lambda.novdv.ru>
>>>>> "PN" == Peter Novodvorsky <nidd@altlinux.ru> writes:
PN> So I've began work on making database backends to gnats
PN> modular. Just now, gnats has two "backends", network (gnatsd)
PN> and filsystem. If we make system of backends modular we could
PN> have SQL backend, etc., etc.
Yes, this is a wanted feature.
PN> Second thing I don't like in GNATS, it doesn't has
PN> ACLs. This modular framework should support them. Here is the
PN> header file that will briefly describe what I mean:
I'm afraid I couldn't understand what kind of ACLs you would like to
have. Could you elaborate?
PN> If everything will be OK in the end following will be
PN> possible:
PN> user -> client -> gnatsd -> SQL server (MySQL,
PN> Postgres)
PN> What do you think of this crazy idea?
I can't see anything crazy in it. :-) Actually I was already asked by my
friend about the possibility of using LDAP as the PR storage.
However, no new features will get into GNATS 4.0. I think the backend
architecture and the MIME handling could be the main feature candidates
for the first non-bug-fix release after 4.0. Of course, we can start
discussing the API and architecture now and you can also work on a
preliminary implementation in the meantime, just don't expect it to have
it in 4.0.
PN> I'm not professional programmer and I would like to discuss
PN> implementation of this feature with maintainer.
OK.
BTW, please note I'll be soon out of Internet for about a week or two.
Regards,
Milan Zamazal
--
Omigod, it's a flame war about a flame war. You know, a meta-flame war!
Kenny Tilton in comp.lang.lisp
next prev parent reply other threads:[~2001-05-28 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 11:32 Peter Novodvorsky
2001-05-28 2:43 ` Yngve Svendsen
2001-05-28 4:34 ` Peter Novodvorsky
2001-06-04 21:53 ` Margaret BRIERTON
2001-06-05 1:35 ` GNATS discussion group Yngve Svendsen
2001-06-05 19:56 ` Margaret BRIERTON
2001-06-06 4:54 ` Yngve Svendsen
2001-06-07 17:04 ` Margaret BRIERTON
2001-06-07 18:15 ` Database Margaret BRIERTON
2001-05-28 14:37 ` Milan Zamazal [this message]
2001-05-29 12:43 ` modular database backends Peter Novodvorsky
2001-06-11 11:53 ` Milan Zamazal
2001-06-13 10:31 ` Peter Novodvorsky
2001-06-17 12:26 ` Milan Zamazal
2001-06-11 11:53 ` access control (was Re: modular database backends) Milan Zamazal
2001-06-13 5:20 ` access control Hans-Albert Schneider
2001-06-17 12:26 ` Milan Zamazal
2001-06-13 10:44 ` access control (was Re: modular database backends) Peter Novodvorsky
2001-05-27 11:35 modular database backends Peter Novodvorsky
2001-05-29 0:11 Dirk Bergstrom
2001-05-29 0:22 ` Bob Kaehms
2001-05-29 1:16 ` Peter Novodvorsky
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=878zjhdvwu.fsf@blackbird.zamazal.org \
--to=pdm@zamazal.org \
--cc=gnats-devel@sources.redhat.com \
--cc=nidd@altlinux.ru \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).