Mercurial Mercurial > oss > FCL > sftools > depl > docscontent / diff
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Symbian3/PDK/Source/GUID-697087D6-C029-51E8-8722-9E2584420276.dita
changeset 12 80ef3a206772
parent 9 59758314f811
child 14 578be2adaf3e 
--- a/Symbian3/PDK/Source/GUID-697087D6-C029-51E8-8722-9E2584420276.dita	Fri Jul 02 12:51:36 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-697087D6-C029-51E8-8722-9E2584420276.dita	Fri Jul 16 17:23:46 2010 +0100
@@ -11,7 +11,7 @@
   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
 <concept xml:lang="en" id="GUID-697087D6-C029-51E8-8722-9E2584420276"><title>SMS Stack Architecture</title><shortdesc>The SMS Stack is a plug-in to the socket server. This section provides the architectural relationships of the SMS stack. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>SMS stack components</title> <ol id="GUID-B7B94BE7-8F08-5104-9741-87600C6B2BB2"><li id="GUID-A354C7A1-7DE5-571F-9DFB-2F3AC90ED12D"><p>SMSPROT - The SMS stack protocol module </p> </li> <li id="GUID-7636FB1A-5162-5136-8ADD-2C4DCE36818A"><p>GSMU - GSM Utility class </p> </li> <li id="GUID-B9C83C25-4727-5992-A40A-83EFDABFE2FF"><p>SMSU - SMS Utility class </p> </li> </ol> <p><b>SMSPROT</b> </p> <p>SMSPROT.prt is a socket server (ESOCK) plug-in DLL implemented with a protocol module suffix <codeph>PRT</codeph>. The main functions of the SMS protocol module are to send queues, receive queues and maintain the connection to the socket server. For more information about SMSPROT, <xref href="GUID-4ADE94EF-346F-541A-B0FB-AF43ADB1C66D.dita">see SMS Protocol Modules</xref>. </p> <p><b>GSMU</b> </p> <p>The GSM Utility (GSMU) class provides some utility functions for the SMS stack. The SMS messages are represented by a <xref href="GUID-FA6D9B1B-3845-3B81-ACBB-34977D3C9631.dita"><apiname>CSmsMessage</apiname></xref> object of the GSMU class. GSMU also provide methods to send and receive the SMS messages through the socket server. For more information about GSMU, <xref href="GUID-A957A1DF-AF81-5A9D-BB44-1B34B2EB809E.dita">see GSM Utilities</xref>. </p> <p><b>SMSU</b> </p> <p>The SMS Utility (SMSU) class provides the base class for active objects of the SMS stack. For more information about SMSU, <xref href="GUID-A4FBD7D4-DCC0-517A-BCAA-D36D8940A64D.dita">see SMS Utilities</xref>. </p> <fig id="GUID-B0D5C075-FE00-5E3B-9F1A-C6F9D45A3BF3"><title>
              SMS Stack Architectural Relationships
-          </title> <image href="GUID-D7AFA78E-4B87-554E-B0A5-1AEEA98B537C_d0e39628_href.png" placement="inline"/></fig> <p>When a client application requests a service from the SMS stack, the SMS stack is loaded by the socket server. The main SMS stack clients are the messaging application, the WAP stack and the third party applications. The WAP stack binds directly to the SMS stack. The messaging applications and other third party applications access the SMS stack as the clients of the socket server. </p> <p>The SMS stack communicates with the ETel (Telephony) server to send, receive, read, write and delete the SMS messages from the Subscriber Identity Module (SIM). </p> <p>The SMS stack uses the message store called as the reassembly store to store the messages passed by the Telephony System plug-in (TSY). The stored messages are then processed. </p> </section> <section><title>Stack initialisation</title> <p>The socket server loads the SMS stack. The socket server loads the stack when one of the clients requests a session with the stack. The load the SMS stack, the socket server searches for the smswap.sms.esk file. The ESK files contain the details of the DLL which creates the SMS stack. The smswap.sms.esk file is located at <codeph>epoc32\data\z\private\101F7989\SOCKET</codeph> and <codeph>epoc32\wins\c\private\101f7989</codeph>. </p> <codeblock id="GUID-70A2081E-A7EB-58AB-852E-53DD4B7C5AF9" xml:space="preserve">
+          </title> <image href="GUID-D7AFA78E-4B87-554E-B0A5-1AEEA98B537C_d0e43862_href.png" placement="inline"/></fig> <p>When a client application requests a service from the SMS stack, the SMS stack is loaded by the socket server. The main SMS stack clients are the messaging application, the WAP stack and the third party applications. The WAP stack binds directly to the SMS stack. The messaging applications and other third party applications access the SMS stack as the clients of the socket server. </p> <p>The SMS stack communicates with the ETel (Telephony) server to send, receive, read, write and delete the SMS messages from the Subscriber Identity Module (SIM). </p> <p>The SMS stack uses the message store called as the reassembly store to store the messages passed by the Telephony System plug-in (TSY). The stored messages are then processed. </p> </section> <section><title>Stack initialisation</title> <p>The socket server loads the SMS stack. The socket server loads the stack when one of the clients requests a session with the stack. The load the SMS stack, the socket server searches for the smswap.sms.esk file. The ESK files contain the details of the DLL which creates the SMS stack. The smswap.sms.esk file is located at <codeph>epoc32\data\z\private\101F7989\SOCKET</codeph> and <codeph>epoc32\wins\c\private\101f7989</codeph>. </p> <codeblock id="GUID-70A2081E-A7EB-58AB-852E-53DD4B7C5AF9" xml:space="preserve">
 #smswap.sms.esk
 
 [sockman]
FCL/sftools/depl/docscontent