martin: doc/architecture windows.sgml,1.7,1.8

[cvs at intevation.de]

Author: martin

Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv8972

Modified Files:
	windows.sgml 
Log Message:
Martin K.: Remove Bynari, added IMAP annotations, XML format, new freebusy


Index: windows.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/windows.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- windows.sgml	3 Oct 2004 18:56:28 -0000	1.7
+++ windows.sgml	5 Oct 2004 06:05:55 -0000	1.8
@@ -1,27 +1,27 @@
 <chapter><title>Windows Kolab Clients</title>
 
 <para>There are multiple Kolab clients on the Windows platform 
-including proprietary plugins for Outlook like Bynari 1.x and
+including proprietary plugins for Outlook like 
 the Toltec Connector.
 </para>
 <para>
 The mainly tested Windows client application to cooperate with the Kolab Server 2.0 and the KDE client Kontact is
-Outlook 2002 or later on Windows 2000 or later with the Toltec Connector plugin installed.
+Outlook 2002 or later on Windows XP with the Toltec Connector plugin installed.
 No modifications are made to this proprietary software. But some optional settings in the
 "Extras->Options" dialog must be made to insure interoperability:</para>
 <para>The following settings have to be made within Outlook to share the freebusy information on the Kolab server.
-By default Outlook uses an anonymous ftp server integrated on an Exchange server to publish the freebusy data. To retrieve
+By default Outlook uses an anonymous ftp server to publish the freebusy data. To retrieve
 freebusy information of paticipants Outlook uses the http method.
 </para>
 
-<para> For ftp configuration within legacy mode of the Kolab server we chose to take a user <filename>freebusy</filename> with
-a password of <filename>freebusy</filename> to restrict the ftp server. The user is fixed in the LDAP directory. The password 
-can at this time be changed with an LDAP editor.
+<para> With Kolab 2 we don't require the legacy ftp upload feature anymore. Instead freebusy data can be requested at anytime from the
+Kolab server which is then generating the data on the fly. This allows for more sophistaced freebusy data independent of the limited Outlook 
+capabilities. E.g. it is possible with Kolab 2 that multiple calendars including group calendars contribute to the freebusy data.
 </para>
 
 <para>
 Due to the fact that the legacy ftp protocol is unsecure we very much discourage the usage of the real user password as stored 
-in the LDAP directory.
+in the LDAP directory in case the legacy ftp upload feature is required to integrate non Kolab 2 clients with the Kolab server.
 </para>
 
 <para> For http access of the freebusy information on the Kolab server a valid username and password has to be given. The credentials
@@ -34,32 +34,29 @@
 <listitem><para>"Einstellungen->Kalenderoptionen"
 "Besprechungsanfragen standardmäßig als iCAL senden"
 "Frei/Gebucht Optionen->Unter dieser URL veröffentlichen"
-	URL: ftp://freebusy:freebusy<kolab server>/%NAME%.vfb
+	URL: empty
 "Frei/Gebucht Optionen->Unter dieser URL suchen"
-	URL: http://<USERNAME>:<PASSOWRD>@<kolab server>/freebusy/%NAME%.vfb </para></listitem>
+	URL: http://<USERNAME>:<PASSOWRD>@<kolab server>/freebusy/%NAME%.ifb </para></listitem>
 <listitem><para> "Email Format"
 "Senden im Nachrichtenformat" : "Nur Text" </para></listitem>
 <listitem><para> "Internet Mail"
 "MIME : Quoted Printable" </para></listitem>
 </orderedlist>
-<para>Outlook with the Toltec Connector 1.7 operates on the IMAP folder significantly different from the KDE client.
+<para>Outlook with the Toltec Connector operates on the IMAP folder slightly differently from the KDE client.
 The file format for storing notes, task lists, calendar events, and contacts is a multi-part
-MIME message with TNEF (Transport Neutral Encapsulation Format) encoded MIME part being the
-actual information carrier. This is a proprietary Microsoft format. However, with the above
+MIME message with an additional TNEF (Transport Neutral Encapsulation Format) encoded MIME part being 
+an additional information carrier. TNEF is a proprietary Microsoft format which serializes MAPI objects. However, with the above
 adjustments made to the configuration of Outlook it can be advised to send and receive calendar
-events, notes, contacts, and task lists via the almost open legacy format we describe later in the appendix.
+events, notes, contacts, and task lists via the almost open format we describe later in the appendix.
 </para>
 
 <sect1><title>Language dependencies</title>
 <para>
 Due to the fact that Microsoft Outlook does not only localize the user visible interface but 
-also internal data including non user visible filenames, directory names, etc. it is not possible 
-to change the language of the Microsoft Outlook without loosing old data.
-</para>
-<para>
-The language used for an account is set either with the first use of Outlook with the 
-corresponding language or set by the administrator in advance in case the KDE client will be used 
-before Outlook.
+also internal data including non user visible filenames, directory names, etc. it was not possible 
+to change the language of the Microsoft Outlook without loosing old data. This problem has been solved
+with Kolab 2 by using IMAP annotations which define the intended purpose of a folder. E.g. it defines that
+a folder independent of its name shall be the default calendar store.
 </para>
 </sect1>
 </chapter>