|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface SessionNotifier
The SessionNotifier
interface defines a connection notifier for
server-side OBEX connections. When a SessionNotifier
is created
and calls acceptAndOpen()
, it will begin listening for clients
to create a connection at the transport layer. When the transport layer
connection is received, the acceptAndOpen()
method will return a
javax.microedition.io.Connection
that is the connection to the
client. The acceptAndOpen()
method also takes a
ServerRequestHandler
argument that will process the requests
from the client that connects to the server.
Method Summary | |
---|---|
Connection |
acceptAndOpen(ServerRequestHandler handler)
Waits for a transport layer connection to be established and specifies the handler to handle the requests from the client. |
Connection |
acceptAndOpen(ServerRequestHandler handler,
Authenticator auth)
Waits for a transport layer connection to be established and specifies the handler to handle the requests from the client and the Authenticator to use to respond to authentication challenge
and authentication response headers. |
Methods inherited from interface javax.microedition.io.Connection |
---|
close |
Method Detail |
---|
Connection acceptAndOpen(ServerRequestHandler handler) throws IOException
SessionNotifier
object that
does not have a ServiceRecord
in the SDDB, the
ServiceRecord
for this object will be added to the SDDB.
This method requests the BCC to put the local device in connectable mode
so that it will respond to connection attempts by clients.
The following checks are done to verify that the service record provided
is valid. If any of these checks fail, then a
ServiceRegistrationException
is thrown.
btgoep
service record, must be present in
the ServiceRecord
associated with this notifier.
ServiceRecord
associated with this notifier must not
have changed the RFCOMM server channel number
This method will not ensure that ServiceRecord
associated
with this notifier is a completely valid service record. It is the
responsibility of the application to ensure that the service record
follows all of the applicable syntactic and semantic rules for service
record correctness.
Note : once an application invokes close()
on any SessionNotifier
, L2CAPConnectionNotifier
, or StreamConnectionNotifer
instance, all pending acceptAndOpen()
methods that have been invoked previously on that instance MUST throw
InterruptedIOException
. This mechanism provides an application
with the means to cancel any outstanding acceptAndOpen()
method
calls.
handler
- the request handler that will respond to OBEX requests
IOException
- if an error occurs in the transport layer
NullPointerException
- if handler
is null
ServiceRegistrationException
- if the structure of the associated service record is
invalid or if the service record could not be added
successfully to the local SDDB. The structure of service
record is invalid if the service record is missing any
mandatory service attributes, or has changed any of the
values described above which are fixed and cannot be
changed. Failures to add the record to the SDDB could be
due to insufficient disk space, database locks, etc.
BluetoothStateException
- if the server device could not be placed in connectable
mode because the device user has configured the device to
be non-connectableConnection acceptAndOpen(ServerRequestHandler handler, Authenticator auth) throws IOException
Authenticator
to use to respond to authentication challenge
and authentication response headers.
SessionNotifier
object that
does not have a ServiceRecord
in the SDDB, the
ServiceRecord
for this object will be added to the SDDB.
This method requests the BCC to put the local device in connectable mode
so that it will respond to connection attempts by clients.
The following checks are done to verify that the service record provided
is valid. If any of these checks fail, then a
ServiceRegistrationException
is thrown.
btgoep
service record, must be present in
the ServiceRecord
associated with this notifier.
ServiceRecord
associated with this notifier must not
have changed the RFCOMM server channel number
This method will not ensure that ServiceRecord
associated
with this notifier is a completely valid service record. It is the
responsibility of the application to ensure that the service record
follows all of the applicable syntactic and semantic rules for service
record correctness.
Note : once an application invokes close()
on any SessionNotifier
, L2CAPConnectionNotifier
, or StreamConnectionNotifer
instance, all pending acceptAndOpen()
methods that have been invoked previously on that instance MUST throw
InterruptedIOException
. This mechanism provides an application
with the means to cancel any outstanding acceptAndOpen()
method
calls.
handler
- the request handler that will respond to OBEX requestsauth
- the Authenticator
to use with this connection; if
null
then no Authenticator
will be
used
IOException
- if an error occurs in the transport layer
NullPointerException
- if handler
is null
ServiceRegistrationException
- if the structure of the associated service record is
invalid or if the service record could not be added
successfully to the local SDDB. The structure of service
record is invalid if the service record is missing any
mandatory service attributes, or has changed any of the
values described above which are fixed and cannot be
changed. Failures to add the record to the SDDB could be
due to insufficient disk space, database locks, etc.
BluetoothStateException
- if the server device could not be placed in connectable
mode because the device user has configured the device to
be non-connectable
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |