martin: doc/kolab-formats kolab-file-format.lyx,1.5,1.6

[cvs at intevation.de]

Author: martin

Update of /kolabrepository/doc/kolab-formats
In directory doto:/tmp/cvs-serv27325

Modified Files:
	kolab-file-format.lyx 
Log Message:
Martin K.: Added index explaining MAPI, TNEF...


Index: kolab-file-format.lyx
===================================================================
RCS file: /kolabrepository/doc/kolab-formats/kolab-file-format.lyx,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- kolab-file-format.lyx	1 Apr 2004 18:14:32 -0000	1.5
+++ kolab-file-format.lyx	1 Apr 2004 18:43:12 -0000	1.6
@@ -748,6 +748,79 @@
  chosing another encoding technology.
  Therefor in order to make a robust Kolab 2.0 storage format TNEF is proposed.
  
+\layout Part*
+
+Index
+\layout Standard
+
+
+\series bold 
+TNEF:
+\series default 
+ Transportation Neutral Encapsulation Format (Microsoft) TNEF is a format
+ for converting a set of MAPI properties a MAPI message into a serial data
+ stream.
+ The TNEF functions are primarily used by transport providers that need
+ to encode MAPI message properties for transmission through a messaging
+ system that does not support those properties directly.
+ For example, an SMTP-based transport uses TNEF to encode properties like
+ PR_SENT_REPRESENTING, which do not have direct representations in the structure
+ of an SMTP message.
+\layout Standard
+
+The TNEF implementation defines several TNEF-specific attributes, each of
+ which corresponds to a particular MAPI property.
+ These attributes are used to encode their respective MAPI properties into
+ the TNEF stream.
+ In addition, a special attribute is defined that can be used to encapsulate
+ any MAPI property that does not have a specific attribute corresponding
+ to it.
+ The reason these attributes are defined instead of simply using a uniform
+ encoding method for all MAPI properties is to enable backward compatibility
+ with non-MAPI-compliant software that is using TNEF such as Microsoft Mail
+ 3.x and its transport providers.
+\layout Standard
+
+
+\series bold 
+MAPI:
+\series default 
+ Messaging Application Program Interface (Messaging Application Programming
+ Interface) A messaging architecture and a client interface component.
+ As a messaging architecture, MAPI enables multiple applications to interact
+ with multiple messaging systems across a variety of hardware platforms.
+ See also MAPI subsystem, messaging system.
+ As a client interface component, MAPI is the complete set of functions
+ and object-oriented interfaces that forms the foundation for the MAPI subsystem
+'s client application and service provider interfaces.
+ In comparison with Simple MAPI, Common Messaging Calls (CMC), and the CDO
+ Library, MAPI provides the highest performance and greatest degree of control
+ to messaging-based applications and service providers.
+ 
+\layout Standard
+
+
+\series bold 
+MAPI object:
+\series default 
+ An object that supports the OLE Component Object Model (COM), implementing
+ one or more interfaces derived from the IUnknown interface.
+ It is implemented or used by a MAPI compliant service provider or client
+ application, or by MAPI itself.
+ 
+\layout Standard
+
+
+\series bold 
+MAPI message storage provider:
+\series default 
+ A MAPI service provider object that manages one or more message stores,
+ handling message distribution, organization, and storage.
+ Message store providers implement the IAttach : IMAPIProp, IMAPIFolder
+ : IMAPIContainer, IMessage : IMAPIProp, IMsgStore : IMAPIProp, IMSLogon
+ : IUnknown, and IMSProvider : IUnknown interfaces.
+ For more information, see Developing a Message Store Provider.
+ 
 \layout Section
 
 GNU Free Documentation License