This repository has been archived by the owner on Nov 16, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 38
/
rfp-0007-Configuration.html
149 lines (126 loc) · 7.46 KB
/
rfp-0007-Configuration.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
<HTML>
<HEAD>
<META Name="Generator" Content="Lotus Word Pro"></META>
<TITLE>RFP-0007 Services Framework Configuration (1999-09-17)</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<CENTER>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="719">
<TR>
<TD WIDTH="29%" ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD WIDTH="43%" ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="MIDDLE">Java Expert Group </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE">Carter/Grimm</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="MIDDLE">Request for Proposal: 0007 </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE">IBM Corporation </TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="MIDDLE">Expires 20 days after: 17-Sep-1999 </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE">1999-09-17 </TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="MIDDLE">rfc-0007.html </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD>
<TD ALIGN="LEFT" VALIGN="MIDDLE"> </TD></TR>
</TABLE></CENTER>
<H2 ALIGN="CENTER">Services Framework Configuration RFP</H2>
<H3>Status of this Memo </H3>
<P>This document suggests the following extension to the OSGi specification for the Open Services Gateway Initiative, and requests discussion. Distribution of this document is unlimited.
<P>
<H3>Abstract </H3>
<P>A key aspect of the Open Services Gateway Initiative Services Framework[1] is the ability to configure the services on the device. This RFP provides some general goals and guidelines and solicits technical submissions that will lead to defining a configuration capability and API that programs can use to get and set configuration properties.
<P>
<H3>Acknowledgment </H3>
<P>The author wants to acknowledge the contributions of the members of the Connected Alliance and OSGi.
<P>
<H3>Introduction </H3>
<P>The Configuration API enables a program to get and set configuration properties on a device.
<H3>Motivation and Rational </H3>
<P>The primary goal of the Configuration API is to enable services to get and set configuration properties. The Configuration API should meet this goal as follows. First, it should provide a consistent application programming interface (API) to use during development of programs. Second, it should provide the flexibility for implementors to "plug-in" different persistent storage mechanisms below the Configuration API.
<P>
<P><FONT SIZE="3">A typical product will be composed of many programs and services. If a product is re-designed in a future version and split into a different set of programs and services, the configuration state should still be usable. Therefore,</FONT> another goal of the Configuration API is to de-couple programs and services from configuration.<FONT SIZE="3"><BR CLEAR="LEFT">
</FONT>
<H3>Technical Discussion </H3>
<P>Configuration Services must provide, at a minimum, the following capabilities and features:
<P>
<UL TYPE="disc">
<LI>Enable services to get and set configuration properties.
<LI>Support notification of events for property changes (e.g. insertion, removal, update)
<LI>Support the Java String, int, long, byte[], byte, and boolean property types.
<LI>Minimize the software requirements for a managed device.
<ul>
<LI>The API should only require the Java profile[2] for the Services Framework.
<LI>Enable services to share common configuration properties.
<LI>Does not require serialization
</ul>
<LI>De-couples the configuration state, storage location, medium, format and policies from services.
</UL>
<H3></H3>
<H3>Security Considerations </H3>
<P>As a request for specification proposals, this document has no direct security considerations. However, the resulting Configuration capability and API should undergo a security review before approval of the API.
<P>
<H3>References </H3>
<P>[1] Jim Mathis, "Services Framework RFP", OSGi RFP-0001, 1999-09-16, rfp-0001.html
<P>[2] Jim Mathis, "Services Framework J2ME Profile RFP", OSGi RFP-0006, 1999-09-17, rfp-0006.html
<P>[3] Garret Swart, "Configuration and Administration of OSGi Services"
<P>[4] Joshua Bloch (Sun) and Mark Pozefsky (IBM), Preferences API, JSR000010, <A HREF="http://java.sun.com/aboutJava/communityprocess/jsr/jsr_010_prefs.html" TARGET="_top">http://java.sun.com/aboutJava/communityprocess/jsr/jsr_010_prefs.html</A>
<P>
<H3>Author's Address </H3>
<H3></H3>
<TABLE CELLSPACING="0" CELLPADDING="5" WIDTH="636">
<TR>
<TD WIDTH="231" ALIGN="LEFT" VALIGN="TOP">First Name:</TD>
<TD WIDTH="179" ALIGN="LEFT" VALIGN="TOP">Keith</TD>
<TD WIDTH="182" ALIGN="LEFT" VALIGN="TOP">Jon</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">Last Name: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">Carter</TD>
<TD ALIGN="LEFT" VALIGN="TOP">Grimm</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">Company Name: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">IBM Corporation</TD>
<TD ALIGN="LEFT" VALIGN="TOP">IBM Corporation</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">Company Division: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">Pervasive Computing</TD>
<TD ALIGN="LEFT" VALIGN="TOP">Pervasive Computing</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">Street Address: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">11400 Burnet Road</TD>
<TD ALIGN="LEFT" VALIGN="TOP">11400 Burnet Road</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">City, State, Country, Postal Code: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">Austin, TX USA 78758</TD>
<TD ALIGN="LEFT" VALIGN="TOP">Austin, TX USA 78758</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">voice: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">+1 512 838 2155</TD>
<TD ALIGN="LEFT" VALIGN="TOP">+1 512 838 9203</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">fax: </TD>
<TD ALIGN="LEFT" VALIGN="TOP">+1 512 838 0169</TD>
<TD ALIGN="LEFT" VALIGN="TOP">+1 512 838 0169</TD></TR>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP">e-mail:</TD>
<TD ALIGN="LEFT" VALIGN="TOP"><A HREF="mailto:[email protected]" TARGET="_top">[email protected]</A></TD>
<TD ALIGN="LEFT" VALIGN="TOP"><A HREF="mailto:[email protected]" TARGET="_top">[email protected]</A></TD></TR>
</TABLE>
<H3></H3>
<H3>Full Copyright Statement </H3>
<P>Copyright (C) The Open Services Gateway Initiative (1999).
<P>All Rights Reserved.
<P>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Open Services Gateway Initiative.
<P>The limited permissions granted above are perpetual and will not be revoked by the Open Services Gateway Initiative or its successors or assigns.
<P>This document and the information contained herein is provided on an "AS IS" basis and THE OPEN SERVICES GATEWAY INITIATIVE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
<HR>
<P>Expires 20 days after: 1999-09-17
</BODY>
</HTML>