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 id="GUID-F7CC81CE-E823-5196-944A-5F7524411A08" xml:lang="en"><title>Registration |
12 <concept id="GUID-F7CC81CE-E823-5196-944A-5F7524411A08" xml:lang="en"><title>Registration and Discovery</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 and Discovery</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 <p>Server applications need to advertise what services they provide |
14 <p>Server applications need to advertise what services they provide and clients |
14 and clients of server application services need to know what implementations |
15 of server application services need to know what implementations of the services |
15 of the services exist. This happens through Apparc's application registration |
16 exist. This happens through Apparc's application registration file system. </p> |
16 file system. </p> |
17 <p>Application registration files have a table in which applications can list |
17 <p>Application registration files have a table in which applications |
18 the service UIDs that they implement. For each service UID listed, there is |
18 can list the service UIDs that they implement. For each service UID |
19 an associated opaque (i.e. not interpreted by the framework) data field which |
19 listed, there is an associated opaque (i.e. not interpreted by the |
20 indicates how the service is implemented by that application. The opaque data |
20 framework) data field which indicates how the service is implemented |
21 field is accessed through an <codeph>LLINK</codeph> into a resource elsewhere |
21 by that application. The opaque data field is accessed through an <codeph>LLINK</codeph> into a resource elsewhere in the application registration |
22 in the application registration file group. The meaning of this opaque data |
22 file group. The meaning of this opaque data field is not known to |
23 field is not known to the framework, it will vary according to the service. |
23 the framework, it will vary according to the service. For some services |
24 For some services the opaque data field may be a name intended for user display, |
24 the opaque data field may be a name intended for user display, for |
25 for others it may be structured data that the service's client-side code can |
25 others it may be structured data that the service's client-side code |
26 interpret. </p> |
26 can interpret. </p> |
27 <fig id="GUID-84072240-5DC6-5900-B767-FD13666A6639"> |
27 <fig id="GUID-84072240-5DC6-5900-B767-FD13666A6639"> |
28 <image href="GUID-7F7A449F-CC19-570C-A6C1-BC470256AA8C_d0e167970_href.png" placement="inline"/> |
28 <image href="GUID-7F7A449F-CC19-570C-A6C1-BC470256AA8C_d0e174063_href.png" placement="inline"/> |
29 </fig> |
29 </fig> |
30 <p>Clients of a service can discover which applications implement a particular |
30 <p>Clients of a service can discover which applications implement |
31 service by using <xref href="GUID-5EEE8745-F483-33C0-A5B1-AEB5544DE2BA.dita"><apiname>RApaLsSession</apiname></xref>. This has a number of APIs |
31 a particular service by using <xref href="GUID-5EEE8745-F483-33C0-A5B1-AEB5544DE2BA.dita"><apiname>RApaLsSession</apiname></xref>. This |
32 for retrieving an application list, filtered to only include applications |
32 has a number of APIs for retrieving an application list, filtered |
33 that implement a particular service. <codeph>RApaLsSession</codeph> can also |
33 to only include applications that implement a particular service. <codeph>RApaLsSession</codeph> can also return other information about server |
34 return other information about server applications, including how the services |
34 applications, including how the services are implemented as described |
35 are implemented as described by the opaque data field. If a service uses the |
35 by the opaque data field. If a service uses the opaque data field |
36 opaque data field to store localised strings to describe implementations, |
36 to store localised strings to describe implementations, these can |
37 these can be shown to the user. If a service uses structured data, a resource |
37 be shown to the user. If a service uses structured data, a resource |
38 reader can be created over the opaque data field to extract the data. </p> |
38 reader can be created over the opaque data field to extract the data. </p> |
39 <p>Also see the 'Service list' section in <xref href="GUID-A6116E8B-9C4A-5B9E-AA8A-BE031408AA2F.dita">Defining |
39 <section id="GUID-F27C5A21-25B3-4179-AC7D-ABA1BA4DD41B"><title>See also</title><p><xref href="GUID-940F3F6E-BA9C-5E19-9AC5-D848B5E175FB.dita">Application Architecture |
40 application icons, captions and properties</xref>. </p> |
40 Overview</xref></p></section> |
41 <section><title>See also</title><p><xref href="GUID-940F3F6E-BA9C-5E19-9AC5-D848B5E175FB.dita">Application |
|
42 Architecture Overview</xref></p></section> |
|
43 </conbody></concept> |
41 </conbody></concept> |