blob: 8c15eb9ad2b48400fd620e5f6a328b0381399d2a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
<!--
$FML: userctl.sgml,v 1.1 2005/07/27 12:21:37 fukachan Exp $
-->
<chapter id="userctl">
<title>
Subscribe / Unsubscribe
</title>
<sect1 id="userctl.deladd">
<title>
Which Map Subscribe/Unsubscribe Is Operated To ?
</title>
<para>
Subscribe/unsubscribe is operated to $primary_*_map.
</para>
<para>
For example,
subscription of remote administrators is operated into
both $primary_admin_member_map and $primary_admin_recipient_map.
Unsubscription of remote administrators is operated into
both $primary_admin_member_map and $primary_admin_recipient_map.
</para>
<para>
Why use primary_*_map ?
If we use admin_member_maps and admin_recipient_maps, it causes a problem.
</para>
<para>
Subscription should be operated into one map. So we should operate it
into primary_*_map.
</para>
<para>
Unsubscription must be same since xxx_maps is composed of different
privileged maps.
</para>
<para>
For example, $member_maps is as follows.
It contais a list of member and a list of remote administrators.
<screen>
member_maps = $primary_member_map
$admin_member_maps
</screen>
So unsubscription operated for $member_maps may cause
unsubscription of remote administrators. It is wrong logic.
</para>
</sect1>
</chapter>
|
