Symbian OS Communications (Symbian Books), страница 83

Whilst there will always be applications thatonly wish to connect using a very specific technology, indeed a specificaccess point – MMS being a prime example – most applications wouldbenefit from the ability to choose between a set of access points whenconnecting to a service; and it would be even better if they receivednotifications about new access points becoming available so they couldconsider switching.

If the application wasn’t even aware of the change ofbearer, it would be ideal!The utopia of seamless roaming offered by technologies such as mobileIP seems to have been slow to arrive on any major scale, so is thereanother step we can take on the way to seamless roaming? Or, indeed, isa non-seamless roaming system good enough for end-user needs?Well the first step must be to try deploying a system that offers thisability to applications – when starting a connection, make a dynamicselection between access points based on their availability; and providesome form of indication of availability of alternate access points duringthe application’s lifetime. In fact, both the E series phones from Nokiaand the UIQ3 phones from Sony Ericsson contain the first of thesetechnologies – the ability to try groups of access points when connectingto allow a more dynamic selection routine.14.3Better ServicesServices are the hardest part of this mix to try and predict – so we’renot even going to try.

By focusing on the other two parts – networksand interaction – Symbian OS enables you to create the next greatservice. A solid foundation of easy-to-use technology is necessary toexplore the next step in services – and that’s what Symbian OS aims toprovide.THE END41114.4 The EndThat’s it for the book. We hope you’ve found it useful. SymbianPress runs surveys from time to time to gather feedback on the various books that are published, so if you’d like to leave us somefeedback, keep an eye on http://developer.symbian.com/main/academy/press for the next survey.Appendix A:Web ResourcesBluetoothwww.bluetooth.orgForum Nokiawww.forum.nokia.comInfrared Data Associationwww.irda.orgInternet Engineering Task Forcewww.ietf.orgOpen Mobile Alliancewww.openmobilealliance.orgSymbian Developer Networkhttp://developer.symbian.comSymbian OS Documentationhttp://developer.symbian.com/main/oslibrary414WEB RESOURCESSymbian Presshttp://developer.symbian.com/main/academy/pressTelephony: 3GPPhttp://www.3gpp.orgUIQ Developer Community Portalhttp://developer.uiq.comAppendix B:Authorizing FlickrMTM to Use YourFlickr AccountThe current way of authorizing any mobile application to use Flickr is touse your desktop browser to log into a Flickr URL which authorizes theapplication.

The web-based authorization produces a temporary codewhich needs to be input into the mobile application as a one-off. Themobile application will now have access to upload to your account.Without this authorization FlickrMTM will always fail with ‘SendingFailed’.Step 1 – Get a Flickr AccountIn order to upload images to Flickr, you must have a Flickr accountwhich can be obtained from www.flickr.com. The basic account is freeof charge and can be used with the FlickrMTM.416AUTHORIZING FLICKRMTM TO USE YOUR FLICKR ACCOUNTStep 2 – Authorize FlickrMTM over the WebWith your desktop browser (or suitably powerful mobile browser), visitthe following URL (signing in if necessary) in order to authorize FlickrUpload.dll to upload photos to your account: www.flickr.com/auth-35520.You will be presented with a page such as this.Click on “OK, I’ll allow it”And you will get a personal authorization code.Your number will be different.STEP 3 – ENTER YOUR AUTHORIZATION CODE ON THE DEVICE417Step 3 – Enter your Authorization Code on the DeviceYou will need to authorize each emulator or device which you wish touse for uploading to Flickr.

You must repeat Step 2 for each device sincethe authorization code expires once authorization has been completed.Open the SendWorkBench application and select the ‘AuthoriseFlickr’ option.Appendix C:SendWorkBench.app GuideThe SendWorkBench application serves as a test application for drivingthe FlickrMTM and as an example for demonstrating the use of the builtin SMS MTM message type.The main display shows four different types of data. This is the data typewhich will be used when selecting ‘Send’ from the menu. For example,by moving the cursor to ‘Long text’, the send dialog will only list MTMswhich support body text with a length of more than 255 characters.420Menu itemSENDWORKBENCH.APP GUIDEInformationSendBrings up the send menu to offer the user achoice of send bearers which can send the itemcurrently highlighted in the main applicationwindowSend TextSends a text using RSendAsSend And Edit TextBrings up the SMS editor with a populatedmessage using RSendAs.SendAs AttachmentUse RSendAs to send sendasexample.jpegusing the FlickrMTMSendAs LinkedUse RSendAs to send sendasexample.jpegusing a link to the file using FlickrMTMSendAs StreamedUse RSendAs to send sendasexample.jpeg bywriting the data into the mail store, and thensending it using FlickrMTMAuthorise FlickrAuthorize FlickrMTM to use upload to yourFlickr account (see Appendix B)ExitClose SendWorkbenchIndex2.5G networks 13, 156, 358see also GERAN3G networks 13, 156, 197–203,211, 358see also UTRAN3GPP specification 157, 197, 201,205, 413A2DP, Bluetooth 12, 65, 81, 120Abort 314Abort command, OBEX 274–5,279–80, 286–7, 289, 314,332, 339–41AbortIndication 332, 339–41abstract concepts, messaging255–6Accept 36–7, 58, 146–8access point names (APNs), GPRS156–9, 162–3, 167–9ACL see asynchronous transportActisys pods 395–6ActivateSniffRequester 92–3active connectionsinformation 196sockets 32, 33–6, 56–62, 196active mode, physical links 71–2,92–3active objects 6–7, 55–62, 102–3,131–2, 208–9, 233–4, 268,305, 311–12, 316–17see also engines; eventsmessaging 233–4problems 59–60active scheduler 60adapters, Device Managementsystem (DM) 367–87Add 141–3, 203Add command, OMA DeviceManagement system 384–5AddAttachment 249–50, 255AddExtensionSetL 201–3AddFilter 363AddHeaderL 293–8, 311–16AddHttpL 292–3AdditionalProtocolDescriptorList 82AddLinkedAttachment 250AddObserverL 234–5addressesESOCK 50–2, 54, 86Internet 31, 54–6, 176–7IP addresses 31, 50, 54–6,147–8, 159, 176–80,185–6sockets 31, 33–4, 50–2, 54–5,86, 97, 127–31, 133–40ADSL connections 358–9advertising displays 69AES-based cipher suites 12agents, SDDB 106–9, 112–18AGT 18AIF files 262aInboxEntry 228–9AllowRoleSwitch 92–3aMessageType 228–9aMsvId 227–9aMsvSession 227–9analog modems 397, 403aOrdering 227–9APIs 3–9, 19–21, 27–62, 130,155, 159–60, 162–204,205–6, 218, 220, 226–32,241–71, 290–342partner-only APIs 5–6RConnection 8–9, 46–50,159–60, 162–204, 205–6,345–9, 360–1APNs (access point names), GPRS156–9, 162–3, 167–9AppendAttachmentL 252–3appendices 413–20applications 3–12, 407–11see also codeexample applications 9future prospects 407, 410–11QoS 156, 158, 197–203, 408testing 7422ARM 10AsByteSeq 295–6ASCII 135–6, 141–3, 404ASSERT 116–18, 261, 324AssertIdle 265–6association concepts, Bluetooth66–7asterisk wildcard 131–2asynchronous callscancellations 185–6messaging 233, 236–7, 248, 267sockets 34–9, 42–5, 55–6,131–2, 151, 182, 185–6,195asynchronous server API, OBEX338–41asynchronous transport (ACL)see also L2CAPconcepts 65, 66, 72–4, 78–82Attach 48–9, 173AttachmentManagerL 226attachmentsfiles 248–50, 252–3, 254–5,263–5messaging concepts 223–6,245–6, 248–50, 252–3,254–5, 263–5AttributeRequest...

106–7,116–18attributes, SDP 74–8, 80, 104–9authentication 12, 22, 67–8, 71–2,97–103, 186–93, 275–8,282–4, 289, 310–12,333–42, 344, 359–62Bluetooth 67–8, 71–2HTTP 344, 359–62OBEX 275–8, 282–4, 289,310–12, 333–42authorization concepts 72,97–103, 186–93AV (audio video) protocols 17, 33,65, 83, 118–24AvailableCipherSuites 186–93AVCTP (audio video controltransport protocol) 17, 33, 83,118–24INDEXAVDTP (audio video distributiontransport protocol) 17, 33, 65,83AVRCP (audio video remotecontrol protocol) 83, 118–24BAFL APIs 353see also Stringpoolbandwidth 61–2, 71, 197–203,407–9baseband see signalling stackbatteries 10–11, 41, 63–6, 70–1,91–3, 408–9BC (binary compatibility) 13–14BCSP protocol 391–4, 404bearer technologies 160–2,163–75, 193–6, 244–5,391–2, 410different bearers 172–3, 193–6,244–5, 391–2, 410disconnections 175IP networks 160–2, 163–75,193–6, 392, 410progress notifications 193–6billing practices, GPRS 157binary compatibility (BC) 13–14Bind 36–7, 183–6blocked operations 38, 40–2Bluetooth 4–20, 27–8, 33, 50, 53,63–124, 126, 160–1, 164–5,243, 245–6, 265, 273–4,278, 286, 287–9, 305–9,318–22, 330, 336, 391–4,403–6, 408–10, 413A2DP 12, 65, 81, 120ACL 65, 66, 72–4advantages 64, 408–10architectural overview 65–6association concepts 66–7authentication 67–8, 71–2AV protocols 65, 83, 118–24batteries 63–6, 91–3, 408–9cables 63–4channel architecture 66CoD (Class of Device) 68,88–91, 112–18, 288, 318concepts 11–20, 33, 50, 53,63–124, 126, 160–1,164–5, 243, 245–6, 265,273–4, 278, 286, 287–9,305–9, 318–22, 330, 336,391–4, 403–6, 408–10,413connectability concept 66–8,83–91, 126, 319–20controller 17, 65–6, 82–3,121–4definition 63–4device class 68–9, 88–91,112–18, 288, 318–22device discovery 66–9, 83–91,112–18, 287–8, 305–8,318–22, 409–10device names 50discoverability concept 66–9,83–91, 112–18, 287–8,305–8, 318–22, 336,409–10emulator 391–4, 403–6error codes 111ESOCK 83example application 112–18,123–4FTP servers 273, 336–7functionality levels 64future prospects 408–10high-level architecture 17historical background 63–4host 17, 65–6, 82–3IP 155, 160–1, 164–5, 409–10IrDA contrasts 126L2CAP 64–6, 72–4, 78–84,93–6, 102–3, 105–6, 111,114–24logical transports 66, 71–4, 91,114–18OBEX 20, 21–2, 65, 69, 76, 83,89–91, 105–6, 245–6,256, 273–4, 278, 286,287–9, 305–8, 309,318–22, 330, 336, 392operating band 63–4OPP 308, 336–7pairability concept 67–8, 88–9,278INDEXPAN profile 11–12, 16–17, 65,83, 90, 155, 164–5, 167,392–5, 408–10passkeys 68, 97–8physical links 66, 68–72, 91–3,112–18piconet topology 66, 69–72ports 80–2, 391–4, 397, 404power management 70–2,91–3, 408–9profiles 11–12, 16–17, 64–5,81, 118–24protocols 11–12, 16–17, 64–6,73–4, 118–24registry 109–11remote control 83, 118–24RFCOMM 74–6, 78–83, 96,102–3, 105–6, 116–18,274, 288, 308, 309, 318S60 84, 86–8, 98–100, 243,392–4SCO/eSCO 65, 66, 72–3SDAP 109, 112–18SDDBs 75–8, 104–9, 318–19SDP 68, 74–8, 80–2, 83, 90,103–9, 112–18, 278,287–8, 307–8, 318–19,336–7security issues 71–2, 97–103,278, 319–20, 338service class 68–9, 74–8,89–91, 104–9, 112–18service discovery 68–9, 74–8,80–2, 83, 86, 90, 103–9,112–18, 287–8, 305–8,318–22, 336, 409–10sockets 83, 93–4, 96–103,114–18speed statistics 126standards 64–6, 73–4Symbian OS 82–124, 391–4technology overview 63–82transport class 66, 91, 114–18UIQ 84, 86–8, 98–100, 393USB 391, 394, 409UWB 408–9v2 architecture 11–12visible devices 66–8BNEP 83body data, HTTP 348–53Body headers, OBEX 276–7, 281,291–304, 309–16, 321–41books 6BSD sockets 180BTCOMM 402–3BTLinkManager 84bt_sock.h 111buffers 55, 59, 61–2, 289–304,308–16, 322–6concepts 55, 59, 61–2OBEX 289, 291–304, 307–16,322–6builder patterns 109built-in applications 166, 213,220–40bus topology 112–18byte-oriented data channelssee also stream socketsconcepts 30–1C++ 3–4, 162C (heap-allocated) classes 6, 102,293–4c32 serial server 10, 15cables, Bluetooth 63–4CActive 54–8, 85–8, 102–3,137–40, 145–8, 208–9,220–1, 233, 268, 290–1Cambridge Silicon Radio (CSR) 393camera phones 11Cancel 265CancelConnect 32, 36CancelHandshake 186–93CancelIndicationCallback 339–41CancelIoctl 42cancellationsasynchronous calls 185–6HTTP 348–9, 353sockets 32, 36, 37–9, 42–5,185–6CancelProgressNotification 47–8CancelRecv 39–42, 186,191–3CancelSend 37–9, 186, 191–3CanCreateEntryL 259–71423capabilities 13, 29, 241–2, 247,252–5, 260–2, 268–9, 361CAPABILITY 13CAppView 208–9case 54–5, 298–9Casira pods 393CBase 114–18, 228, 293CBaseMtm 259CBaseMtmUi 259CBaseMtmUiData 259CBaseServerMtm 259CBluetoothSocket 93–4,96–7, 102–3, 113–18CBTDevice 110–11CBTDeviceDiscoverer 85–91CBTRegistryResponse 110–11CBufFlat 301–4CCDIARecord 168–70CCertificate 348–9CCnvCharacterSetConverter 136–40CCommsDatabase 167CD 129cdbcols.h 196cdbv3.dat 399CDialer 208–9CDMA 205CED 398, 403–4CEDDUMP 398CEikonEnv 244, 252–3see also Send dialogscell IDs 206–7cellular modem see signalling stackCentral Repository 223certificates, secure sockets 186–93,348–9CF (compact flash) 393CFG files 398CFlickrClientMtm 259CFlickrDataMtm 259CFlickRestAPI 266–7CFlickrMtmClient 259CFlickrMtmServer 259CFlickrMtmUi 259, 262–3CFlickrMtmUiData 259CFlickrRestrAPI 344, 346,349, 354–5CFlickrServerMtm 259, 265–6CFlickrUIMtm 259424CFlickServerMtm 266–8CGetter 208–9CGetWebPage 53–62ChangeEntryL 234chapters, reading guide 9character sets 134–43ChildDataL 229–30ChildrenL 229ChildrenWithMtmL 229ChildURIListL 384CHttpConnectionInfo 346–7chunked transfer encoding 22CIdentifiableSocket 114–18CImageUploadOperation 263CImEmailMessage 225–6, 231CImHeader 230–2CInfiniBTEngine 118CInformer 208–9cipher suites 12, 186–93circuit-switched networks 28, 205see also CSD; GSMconcepts 28, 205CIrDeregisterLocalService 144CIrDeviceDiscoverer 130–40CIrInboundConnnection147–8CIrOutboundConnnection145–6CIrServiceDiscoverer137–40Class of Device (CoD), Bluetooth68, 88–91, 112–18, 288, 318classessee also C...; M...; R...;T...FlickrMTM 258–9HTTP 344–64IP 162–3OBEX 290–1, 293–306, 316–33Send dialogs 250–5types 6wrapper classes 27, 51, 52,55–62, 96–7, 102–3CleanupStack::Pop 297–8,311–13CleanupStack::PopAndDestroy 115, 170, 247, 250,255, 355INDEXCleanupStack::PushL 115,168–70, 238, 247, 249,295–9, 311–12ClearHintBitL 142–3CLIENT 402–3client APIsHTTP 344–64OBEX 290, 304–16, 333–42client MTMs 20–1, 220–3, 230–1,246–50, 256–71see also message-type modulesconcepts 246–50, 256–71server MTMs 264–5client sockets, IrDA 144–6client-server framework 6, 21–2,29–62, 144–8, 220–2,246–50, 274–9, 290,304–42, 343–64see also server.