From 02f0eb5231edfb665704bd0cfd9bfbe5ec59fae1 Mon Sep 17 00:00:00 2001
From: fukachan <fukachan>
Date: Wed, 27 Jul 2005 12:21:35 +0000
Subject: sync and translated.

---
 fml/doc/en/tutorial/internals/userctl.sgml | 57 ++++++++++++++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 fml/doc/en/tutorial/internals/userctl.sgml

(limited to 'fml/doc/en/tutorial/internals/userctl.sgml')

diff --git a/fml/doc/en/tutorial/internals/userctl.sgml b/fml/doc/en/tutorial/internals/userctl.sgml
new file mode 100644
index 00000000..29bb95d5
--- /dev/null
+++ b/fml/doc/en/tutorial/internals/userctl.sgml
@@ -0,0 +1,57 @@
+<!--
+   $FML: userctl.sgml,v 1.3 2004/10/06 09:07:40 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>
-- 
cgit v1.2.1