7 Nokia Corporation - initial contribution. |
7 Nokia Corporation - initial contribution. |
8 Contributors: |
8 Contributors: |
9 --> |
9 --> |
10 <!DOCTYPE concept |
10 <!DOCTYPE concept |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept xml:lang="en" id="GUID-340C57A4-B799-502D-8B86-39955E2F4268"><title> Creating an ESK File Tutorial</title><shortdesc>This topic describes how to create an ESK file. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Introduction</title> <p>An <codeph>ESK</codeph> file is a text file that specifies the order of the protocol modules. The socket server loads the protocol modules. </p> <p>The <codeph>ESK</codeph> file has two sections. The first section specifies the name of the new hook. The second section specifies the name of the file. The name of the file must have the extension and cannot have the full path name. </p> </section> <section><title>Location of the ESK file </title> <p>The location of the ESK file is based on the OS version and the kernel architecture. In the Emulator, the ESK file is found in the location <codeph>winscw\c\private\101F7989\ESock\</codeph>. On the hardware, the ESK file is found in the location <codeph>Z:\private\101F7989\ESock\</codeph>. </p> <p>Symbian OS v9.X and later supports only EKA2 architecture and <codeph>101F7989</codeph> specifies the Secure Identifier (SID). </p> </section> <section><title>Procedure</title> <ol id="GUID-ACE2F663-AFFE-544F-84B3-22BDA622240D"><li id="GUID-DED4A791-FFA9-54DC-AC5D-2286CFC4D397"><p>Create a new <codeph>ESK</codeph> file for every hook that binds the hook to another hook. </p> </li> <li id="GUID-B578104C-3971-59F8-B1E1-1672A1209B22"><p>To bind the hook to other protocols <codeph>bindto</codeph> and <codeph>bindfrom</codeph> directives must be used. The <codeph>bindto</codeph> directive forward data packets from one hook to other hooks and upper layer protocols. The <codeph>bindfrom</codeph> directive receives the data packets from IP6. </p> </li> </ol> </section> <example><title>ESK file example</title> <p>The following code is an example of an <codeph>ESK</codeph> file: </p> <codeblock id="GUID-93D2CD8F-504F-5588-B4E6-741E0EE69BE6" xml:space="preserve"> |
12 <concept id="GUID-340C57A4-B799-502D-8B86-39955E2F4268" xml:lang="en"><title> Creating |
|
13 an ESK File Tutorial</title><shortdesc>This topic describes how to create an ESK file. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 |
|
15 <section id="GUID-C40428B0-C6A8-4FAA-8943-2FC8BC98D8D5"><title>Introduction</title> <p>An <codeph>ESK</codeph> file is a |
|
16 text file that specifies the order of the protocol modules. The socket server |
|
17 loads the protocol modules. </p> <p>The <codeph>ESK</codeph> file has two |
|
18 sections. The first section specifies the name of the new hook. The second |
|
19 section specifies the name of the file. The name of the file must have the |
|
20 extension and cannot have the full path name. </p> </section> |
|
21 <section id="GUID-F7164347-5807-4A2F-A64C-0B9B1E4E90C9"><title>Location of the ESK file </title> <p>The location of the ESK |
|
22 file is based on the OS version and the kernel architecture. In the Emulator, |
|
23 the ESK file is found in the location <codeph>winscw\c\private\101F7989\ESock\</codeph>. |
|
24 On the hardware, the ESK file is found in the location <codeph>Z:\private\101F7989\ESock\</codeph>. </p> <p>Symbian |
|
25 platform supports only EKA2 architecture and <codeph>101F7989</codeph> specifies |
|
26 the Secure Identifier (SID). </p> </section> |
|
27 <section id="GUID-22DC0270-E891-4468-B7EA-868C8F9F4457"><title>Procedure</title> <ol id="GUID-ACE2F663-AFFE-544F-84B3-22BDA622240D"> |
|
28 <li id="GUID-DED4A791-FFA9-54DC-AC5D-2286CFC4D397"><p>Create a new <codeph>ESK</codeph> file |
|
29 for every hook that binds the hook to another hook. </p> </li> |
|
30 <li id="GUID-B578104C-3971-59F8-B1E1-1672A1209B22"><p>To bind the hook to |
|
31 other protocols <codeph>bindto</codeph> and <codeph>bindfrom</codeph> directives |
|
32 must be used. The <codeph>bindto</codeph> directive forward data packets from |
|
33 one hook to other hooks and upper layer protocols. The <codeph>bindfrom</codeph> directive |
|
34 receives the data packets from IP6. </p> </li> |
|
35 </ol> </section> |
|
36 <example><title>ESK file example</title> <p>The following code is an example |
|
37 of an <codeph>ESK</codeph> file: </p> <codeblock id="GUID-93D2CD8F-504F-5588-B4E6-741E0EE69BE6" xml:space="preserve"> |
13 [yourhook] |
38 [yourhook] |
14 protocols= tcp,ip |
39 protocols= tcp,ip |
15 |
40 |
16 [ip] |
41 [ip] |
17 filename=tcpip6.prt |
42 filename=tcpip6.prt |
18 index=1 |
43 index=1 |
19 </codeblock> </example> <section><title>How to Create an ESK file</title> <p>The following code is an example to create an <codeph>ESK</codeph> file to bind a new hook called myhook: </p> <codeblock id="GUID-0D7F9FD9-53C6-5ED8-B2A6-C2CCEEE4F121" xml:space="preserve"> |
44 </codeblock> </example> |
|
45 <section id="GUID-C338C04F-C3C6-4F83-8CB4-AECD41F0515B"><title>How to Create an ESK file</title> <p>The following code is |
|
46 an example to create an <codeph>ESK</codeph> file to bind a new hook called |
|
47 myhook: </p> <codeblock id="GUID-0D7F9FD9-53C6-5ED8-B2A6-C2CCEEE4F121" xml:space="preserve"> |
20 [sockman] |
48 [sockman] |
21 protocols=myhook,ip6 |
49 protocols=myhook,ip6 |
22 |
50 |
23 [myhook] |
51 [myhook] |
24 filename=myhook.prt |
52 filename=myhook.prt |
25 index=2 |
53 index=2 |
26 bindfrom=ip6 |
54 bindfrom=ip6 |
27 </codeblock> </section> </conbody><related-links><link href="GUID-6998404B-CC51-5337-B04F-8444C32B99C9.dita"><linktext>Writing an Inbound |
55 </codeblock> </section> |
28 Hook</linktext> </link> </related-links></concept> |
56 </conbody><related-links> |
|
57 <link href="GUID-6998404B-CC51-5337-B04F-8444C32B99C9.dita"><linktext>Writing an |
|
58 Inbound Hook</linktext></link> |
|
59 </related-links></concept> |