Re: [GnomeMeeting-devel-list] New feature - controlling the calls (allow/deny)
- From: m-redlich t-online de (Matthias Redlich)
- To: GM devel list <gnomemeeting-devel-list gnome org>
- Subject: Re: [GnomeMeeting-devel-list] New feature - controlling the calls (allow/deny)
- Date: 05 Dec 2002 23:31:22 +0100
Hi again,
due to damien claimed that I didn't explain my solution very well I'll
now try again:
My idea is to create just 2 simple lists (I already mentioned that they
are similar to the hosts.deny and hosts.allow of unix). With this
solution the filter would be a mix of an 'easy-to-use' and powerful
tool. Newbies wouldn't have problems to use it, advanced users had a
powerful tool to define their filter rules.
OK, here we go. My proposal would have just two list: reject list,
accept list. Thus you can have two basic configurations/policies:
1. accept all calls: with this configuration all calls are accepted. You
just have to add the users you want to avoid to the reject-list. I would
propose to use this as the default configuration because newbies
wouldn't have to change anything to use GM.
2. reject all calls: with this configuration all calls are rejected by
default. You have to add your friends to the accept-list to allow them
to call you. Nobody except of your friends would disturb you.
As you can see, this filter is easy to configure but can become quite
powerful if you have a lot of rules. In my opinion it is easy for
newbies to understand this method, otherwise they don't have to touch
it.
Damien mentioned that he also wants to differ between "auto-answer" and
popup-message. This could also be realised with a second option in the
accept rules, for instance.
The accept rule could look like this:
damien auto-answer
matthias popup
matti auto-answer
...
Everything clear? If not, please ask.
Btw, IPFilter (a packet filter) uses this method too.
Cheers,
Matthias
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]