open() that were described in Chapter 4
(RFCOMM), Chapter 5 (OBEX), and Chapter 8 (L2CAP). The Push Registry
also allows a developer to restrict devices that may use the service
via the AllowSender parameter that is passed in with the registry
request.
Once the connection string is registered with the Push Registry, a
service record is created based on the connection string. The Push Registry
places the service record in the SDDB and activates the service
record. The service record may be modified by a MIDlet to provide
more information to clients that may wish to use the service. When a
client connects to the service, a device may deactivate the service record
and stop accepting connections for the service.
274 Chapter Nine: Push Registry
10 CHAPTER Closing
Remarks
Software standards often are vital to the success of communications
technologies. An effective software standard will encourage development
of a number of successful applications. Java Speci?¬?cation
Request-82, developed by the Java Community Process, standardized
the Java APIs for Bluetooth Wireless Technology. JABWT makes it possible
to write an application once and then run the application on any
Java-enabled device that supports JABWT. Because JABWT was developed
with the participation of several companies that develop Bluetooth
stacks, we believe it will be possible to implement JABWT in conjunction
with a wide variety of Bluetooth stacks.
Pages:
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333