|
1 From: "odc" <matthewf@msexchange2k.closedtest.intra> |
|
2 To: <matthewf@msexchange2k.closedtest.intra> |
|
3 Subject: test21_1 |
|
4 Date: Sun, 23 May 2004 19:03:51 +0530 |
|
5 MIME-Version: 1.0 |
|
6 Content-Type: multipart/mixed; |
|
7 boundary="----=_NextPart_000_0087_01C440F8.AF553300" |
|
8 X-Priority: 3 |
|
9 X-MSMail-Priority: Normal |
|
10 X-Mailer: Microsoft Outlook Express 5.50.4922.1500 |
|
11 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800 |
|
12 |
|
13 This is a multi-part message in MIME format. |
|
14 |
|
15 ------=_NextPart_000_0087_01C440F8.AF553300 |
|
16 Content-Type: multipart/alternative; |
|
17 boundary="----=_NextPart_001_0088_01C440F8.AF553300" |
|
18 |
|
19 |
|
20 ------=_NextPart_001_0088_01C440F8.AF553300 |
|
21 Content-Type: text/plain; |
|
22 charset="iso-8859-1" |
|
23 Content-Transfer-Encoding: quoted-printable |
|
24 |
|
25 Internet access on the Nokia 9200 Series Communicator is necessarily = |
|
26 limited by the speed of the phone's GSM connection. As a consequence, = |
|
27 testing and debugging Internet-based applications on hardware can be = |
|
28 both expensive and tedious. The RAS IAP application alleviates this = |
|
29 problem by enabling you to connect to the Internet over a much faster = |
|
30 serial connection, via your PCThe application demonstrates how the = |
|
31 Symbian OS Communications database (CommDb) API may be used to configure = |
|
32 an Internet Access Point (IAP). To some extent it also shows the common = |
|
33 paradigm for using most DBMS derived APIs.An Internet Access Point = |
|
34 defines ISP, modem, charge card and location records that can be used = |
|
35 together to make an Internet connection. The IAP for the RAS connection = |
|
36 specifies an ISP and modem record (charge card and location records are = |
|
37 required for this type of IAP). The CommDb is a standard DBMS database. = |
|
38 Modems, ISPs, charge cards, locations, IAPs etc are all stored in their = |
|
39 own tables within the database. There may be a number of records within = |
|
40 each table (e.g., there may be a number of IAPs, modems, ISPs, etc.). As = |
|
41 described in the preceding section, each IAP record defines the set of = |
|
42 ISP, modem, charge card, and location that can be used together. In = |
|
43 other words, an IAP record defines a set of records the other tables.The = |
|
44 implication of the above statement is that sets of CommDb records are = |
|
45 accessed through their associated table. The other implication is that = |
|
46 you cannot create an IAP record until you have already created the other = |
|
47 records. Finally, the fact that there may be many records in a table = |
|
48 implies that each record must be uniquely identified.2. Copy an existing = |
|
49 CommDb that has a correctly configured IAP. This method "works", but has = |
|
50 several problems. Firstly, Symbian does not guarantee that the CommDb = |
|
51 will be binary compatible between releases. In practice this has not = |
|
52 been an issue, but it is something to keep in mind. Secondly, while you = |
|
53 are using your RAS IAP, you don't have access to IAPs you configured in = |
|
54 the "real" CommDb. Finally, and most importantly, CommDb configuration = |
|
55 should be targeted to the platform; The CommDb that you use for RAS = |
|
56 connections may well disable some of your other phone services.. Add an = |
|
57 IAP to your existing (proven) CommDb using RAS IAP. The advantage of = |
|
58 this method is that you get to retain the CommDb that your manufacturer = |
|
59 put onto the phone, and therefore can expect the device to continue to = |
|
60 work with the new IAP! Also, the CommDb API is binary compatible between = |
|
61 releases, so you can rely on this method as you change phone. It is also = |
|
62 by far the simplest method! Rather than coding the application from = |
|
63 first principles, I used the standard Minimal Eikon Application = |
|
64 Developer (MEAD) and Menu Builder tools to create an application that I = |
|
65 could easily customize. I then modified the engine to write to the = |
|
66 CommDb, and the UI to call the engine as appropriate. Each of these = |
|
67 exports calls non-exported functions to actually implement the creation = |
|
68 and deletion of the components of the IAP |
|
69 ------=_NextPart_001_0088_01C440F8.AF553300 |
|
70 Content-Type: text/html; |
|
71 charset="iso-8859-1" |
|
72 Content-Transfer-Encoding: quoted-printable |
|
73 |
|
74 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|
75 <HTML><HEAD> |
|
76 <META http-equiv=3DContent-Type content=3D"text/html; = |
|
77 charset=3Diso-8859-1"> |
|
78 <META content=3D"MSHTML 5.50.4926.2500" name=3DGENERATOR> |
|
79 <STYLE></STYLE> |
|
80 </HEAD> |
|
81 <BODY bgColor=3D#ffffff> |
|
82 <DIV><FONT face=3DArial size=3D2>Internet access on the Nokia 9200 = |
|
83 Series=20 |
|
84 Communicator is necessarily limited by the speed of the phone's GSM = |
|
85 connection.=20 |
|
86 As a consequence, testing and debugging Internet-based applications on = |
|
87 hardware=20 |
|
88 can be both expensive and tedious. The RAS IAP application alleviates = |
|
89 this=20 |
|
90 problem by enabling you to connect to the Internet over a much faster = |
|
91 serial=20 |
|
92 connection, via your PCThe application demonstrates how the Symbian OS=20 |
|
93 Communications database (CommDb) API may be used to configure an = |
|
94 Internet Access=20 |
|
95 Point (IAP). To some extent it also shows the common paradigm for using = |
|
96 most=20 |
|
97 DBMS derived APIs.An Internet Access Point defines ISP, modem, charge = |
|
98 card and=20 |
|
99 location records that can be used together to make an Internet = |
|
100 connection. The=20 |
|
101 IAP for the RAS connection specifies an ISP and modem record (charge = |
|
102 card and=20 |
|
103 location records are required for this type of IAP). The CommDb is a = |
|
104 standard=20 |
|
105 DBMS database. Modems, ISPs, charge cards, locations, IAPs etc are all = |
|
106 stored in=20 |
|
107 their own tables within the database. There may be a number of records = |
|
108 within=20 |
|
109 each table (e.g., there may be a number of IAPs, modems, ISPs, etc.). As = |
|
110 |
|
111 described in the preceding section, each IAP record defines the set of = |
|
112 ISP,=20 |
|
113 modem, charge card, and location that can be used together. In other = |
|
114 words, an=20 |
|
115 IAP record defines a set of records the other tables.The implication of = |
|
116 the=20 |
|
117 above statement is that sets of CommDb records are accessed through = |
|
118 their=20 |
|
119 associated table. The other implication is that you cannot create an IAP = |
|
120 record=20 |
|
121 until you have already created the other records. Finally, the fact that = |
|
122 there=20 |
|
123 may be many records in a table implies that each record must be uniquely = |
|
124 |
|
125 identified.2. Copy an existing CommDb that has a correctly configured = |
|
126 IAP. This=20 |
|
127 method "works", but has several problems. Firstly, Symbian does not = |
|
128 guarantee=20 |
|
129 that the CommDb will be binary compatible between releases. In practice = |
|
130 this has=20 |
|
131 not been an issue, but it is something to keep in mind. Secondly, while = |
|
132 you are=20 |
|
133 using your RAS IAP, you don't have access to IAPs you configured in the = |
|
134 "real"=20 |
|
135 CommDb. Finally, and most importantly, CommDb configuration should be = |
|
136 targeted=20 |
|
137 to the platform; The CommDb that you use for RAS connections may well = |
|
138 disable=20 |
|
139 some of your other phone services.. Add an IAP to your existing (proven) = |
|
140 CommDb=20 |
|
141 using RAS IAP. The advantage of this method is that you get to retain = |
|
142 the CommDb=20 |
|
143 that your manufacturer put onto the phone, and therefore can expect the = |
|
144 device=20 |
|
145 to continue to work with the new IAP! Also, the CommDb API is binary = |
|
146 compatible=20 |
|
147 between releases, so you can rely on this method as you change phone. It = |
|
148 is also=20 |
|
149 by far the simplest method! Rather than coding the application from = |
|
150 first=20 |
|
151 principles, I used the standard Minimal Eikon Application Developer = |
|
152 (MEAD) and=20 |
|
153 Menu Builder tools to create an application that I could easily = |
|
154 customize. I=20 |
|
155 then modified the engine to write to the CommDb, and the UI to call the = |
|
156 engine=20 |
|
157 as appropriate. Each of these exports calls non-exported functions to = |
|
158 actually=20 |
|
159 implement the creation and deletion of the components of the=20 |
|
160 IAP</FONT></DIV></BODY></HTML> |
|
161 |
|
162 ------=_NextPart_001_0088_01C440F8.AF553300-- |
|
163 |
|
164 ------=_NextPart_000_0087_01C440F8.AF553300 |
|
165 Content-Type: image/jpeg; |
|
166 name="MS.JPG" |
|
167 Content-Transfer-Encoding: base64 |
|
168 Content-Disposition: attachment; |
|
169 filename="MS.JPG" |
|
170 |
|
171 /9j/4AAQSkZJRgABAgIAAAAAAAD/4QAKUElDAAEyMgD/wAARCAAgACADAREAAhEBAxEB/9sAhAAZ |
|
172 ERIVEg8ZFRQVHBoZHSU+KCUiIiVMNjktPlpPX11ZT1dVZHCPeWRqh2tVV32qfoeUmaCioGB4sL2v |
|
173 nLuPnaCaARocHCUgJUkoKEmaZ1dnmpqampqampqampqampqampqampqampqampqampqampqampqa |
|
174 mpqampqampqampqampr/xAGiAAABBQEBAQEBAQAAAAAAAAAAAQIDBAUGBwgJCgsQAAIBAwMCBAMF |
|
175 BQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGhCCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkq |
|
176 NDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqi |
|
177 o6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+gEA |
|
178 AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoLEQACAQIEBAMEBwUEBAABAncAAQIDEQQFITEGEkFR |
|
179 B2FxEyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RFRkdISUpTVFVW |
|
180 V1hZWmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrC |
|
181 w8TFxsfIycrS09TV1tfY2dri4+Tl5ufo6ery8/T19vf4+fr/2gAMAwEAAhEDEQA/AOnkdYo2kdgq |
|
182 ICzE9gKAONGoXbXkt7DM0LStu2dV28AAjoeB1rGVS0j0qWCU6SbdmzWs/EseVj1BBC56SJyh/qK1 |
|
183 i+ZaHHWoTou0jcjkSVA8bq6NyGU5BpmJl60Wu2j0yJ9rSgvK2M7UHtkdTgfnWNeqqUOYqO5nXFjF |
|
184 YaXO1yiSSsxEcqrynGFyewyM/jjnv50Krq1FyOy6rudTqSnU572f5GHK8Uqlw5DAYUev4V7ND29C |
|
185 ajBau33G2IlQrwc3Lbb/AIYsaM15/aEUFlO8XmH58cgDucHjpXoY2lSgk0rNnlRbZu290La8uH1F |
|
186 Xtprh8qZPubQDtUMCRwOvTk183jaVWbTSukbRaMi4iubeeT7ScTyKQ7Bgd6ng9O3pnHt04uEoSj7 |
|
187 uy/A5ajnBtt7mYqs0mzADdxjgV9BHEQw+Hi4O/z+8G0lc6jwpYeVbveyD55vlT2Uf4n+QrkrVnWn |
|
188 zM2SsjekjSVCkiK6NwVYZBrEZiXvhtG+exl8lgMCN8snc4HcckmocEyJQUtzI/s67e9jsZoWiaU4 |
|
189 LdRtHUg9+P5iojTtIyjStK7OyjRYo1jRQqIAqgdgK2Og/9k= |
|
190 |
|
191 ------=_NextPart_000_0087_01C440F8.AF553300 |
|
192 Content-Type: text/plain; |
|
193 name="3kb.txt" |
|
194 Content-Transfer-Encoding: quoted-printable |
|
195 Content-Disposition: attachment; |
|
196 filename="3kb.txt" |
|
197 |
|
198 Internet access on the Nokia 9200 Series Communicator is necessarily = |
|
199 limited by the speed of the phone's GSM connection. As a consequence, = |
|
200 testing and debugging Internet-based applications on hardware can be = |
|
201 both expensive and tedious. The RAS IAP application alleviates this = |
|
202 problem by enabling you to connect to the Internet over a much faster = |
|
203 serial connection, via your PCThe application demonstrates how the = |
|
204 Symbian OS Communications database (CommDb) API may be used to configure = |
|
205 an Internet Access Point (IAP). To some extent it also shows the common = |
|
206 paradigm for using most DBMS derived APIs.An Internet Access Point = |
|
207 defines ISP, modem, charge card and location records that can be used = |
|
208 together to make an Internet connection. The IAP for the RAS connection = |
|
209 specifies an ISP and modem record (charge card and location records are = |
|
210 required for this type of IAP). The CommDb is a standard DBMS database. = |
|
211 Modems, ISPs, charge cards, locations, IAPs etc are all stored in their = |
|
212 own tables within the database. There may be a number of records within = |
|
213 each table (e.g., there may be a number of IAPs, modems, ISPs, etc.). As = |
|
214 described in the preceding section, each IAP record defines the set of = |
|
215 ISP, modem, charge card, and location that can be used together. In = |
|
216 other words, an IAP record defines a set of records the other tables.The = |
|
217 implication of the above statement is that sets of CommDb records are = |
|
218 accessed through their associated table. The other implication is that = |
|
219 you cannot create an IAP record until you have already created the other = |
|
220 records. Finally, the fact that there may be many records in a table = |
|
221 implies that each record must be uniquely identified.2. Copy an existing = |
|
222 CommDb that has a correctly configured IAP. This method "works", but has = |
|
223 several problems. Firstly, Symbian does not guarantee that the CommDb = |
|
224 will be binary compatible between releases. In practice this has not = |
|
225 been an issue, but it is something to keep in mind. Secondly, while you = |
|
226 are using your RAS IAP, you don't have access to IAPs you configured in = |
|
227 the "real" CommDb. Finally, and most importantly, CommDb configuration = |
|
228 should be targeted to the platform; The CommDb that you use for RAS = |
|
229 connections may well disable some of your other phone services.. Add an = |
|
230 IAP to your existing (proven) CommDb using RAS IAP. The advantage of = |
|
231 this method is that you get to retain the CommDb that your manufacturer = |
|
232 put onto the phone, and therefore can expect the device to continue to = |
|
233 work with the new IAP! Also, the CommDb API is binary compatible between = |
|
234 releases, so you can rely on this method as you change phone. It is also = |
|
235 by far the simplest method! Rather than coding the application from = |
|
236 first principles, I used the standard Minimal Eikon Application = |
|
237 Developer (MEAD) and Menu Builder tools to create an application that I = |
|
238 could easily customize. I then modified the engine to write to the = |
|
239 CommDb, and the UI to call the engine as appropriate. Each of these = |
|
240 exports calls non-exported functions to actually implement the creation = |
|
241 and deletion of the components of the IAP |
|
242 ------=_NextPart_000_0087_01C440F8.AF553300-- |