Symbian3/SDK/Source/GUID-4CEB52EC-8F08-53B7-A900-AF163316D442.dita
author Dominic Pinkman <Dominic.Pinkman@Nokia.com>
Thu, 21 Jan 2010 18:18:20 +0000
changeset 0 89d6a7a84779
permissions -rw-r--r--
Initial contribution of Documentation_content according to Feature bug 1266 bug 1268 bug 1269 bug 1270 bug 1372 bug 1374 bug 1375 bug 1379 bug 1380 bug 1381 bug 1382 bug 1383 bug 1385

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License 
"Eclipse Public License v1.0" which accompanies this distribution, 
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
    Nokia Corporation - initial contribution.
Contributors: 
-->
<!DOCTYPE concept
  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-4CEB52EC-8F08-53B7-A900-AF163316D442" xml:lang="en"><title>Quick
Start</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>The Messaging Middleware module provides application-level APIs to handle
the storage and transport of different type of messages. The message types
that are currently supported are email (POP3, IMAP4 and SMTP), SMS, BIO and
OBEX messages. </p>
<section id="GUID-A61CB959-EF05-49DA-BEEB-E88CC2F78302"><title>Getting started with Messaging Middleware</title> <p>Messaging
Middleware provides APIs to build highly-featured message client applications
to manipulate messages in Message Store and to enable storage of messages
in the Message Store. It also provides support for creating plug-ins to handle
individual messaging protocols. </p> </section>
<section id="GUID-46E6E94B-F973-477A-905D-2EA80C81624B"><title>Architecture</title> <p>The Messaging Middleware architecture
comprises of many components to form the Messaging Framework. The framework
provides plug-ins (polymorphic MTMs) to manage different type of messages.
The set of components that make up a plug-in module is called an Message Type
Module (MTM). All interactions with lower-level communication protocols, such
as, TCP/IP, are performed by MTMs. The Messaging Framework provides APIs to
enable storage of messages in the Message Store. It also provides APIs to
manipulate messages in the Message Store.</p><fig id="GUID-79BA59FD-0DC0-45FF-8882-1E4CB08F5A2C">
<image href="GUID-A950288B-D9D8-59E3-9F4C-0AEE2FC77E38_d0e251491_href.jpg" placement="inline"/>
</fig></section>
<section id="GUID-785B1C63-F749-4D9F-AF08-A38C66DBE4DA"><title>Documentation and examples</title><p>The following sections
list tutorials and example applications that can be referred while creating
messaging applications:</p><ul>
<li><xref href="GUID-734582DF-DC6B-51AD-BB93-3A17FF02BEC4.dita">Message Server
and Store Configuration Tutorial</xref></li>
<li><xref href="GUID-F3E5D412-BEB5-4E0F-9CDE-1DF3F9302BC3.dita">MTM Implementation
Tutorial</xref></li>
<li><xref href="GUID-2F9BCBC4-A657-5B16-824E-5E96DA22AD00.dita">Search-Sort Tutorial</xref></li>
<li><xref href="GUID-1963A487-D6A7-4225-8D0C-EC5FAB746854.dita">Attachment Tutorial</xref></li>
</ul></section>
</conbody><related-links>
<link href="GUID-C1F71368-E35A-512D-A9DF-F81491F35E62.dita"><linktext>Messaging
Middleware Concepts</linktext></link>
</related-links></concept>