public interface SessionNotifier
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.Modifier and Type | Method and Description |
---|---|
ObexSession |
acceptAndOpen(ServerRequestHandler handler)
Waits for a transport layer connection to be established and specifies
the handler to handle the requests from the client.
|
ObexSession |
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. |
ObexSession 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.
handler
- the request handler that will respond to OBEX requestsIOException
- if an error occurs in the transport layerNullPointerException
- if handler
is null
ObexSession 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.
handler
- the request handler that will respond to OBEX requestsauth
- the Authenticator
to use with this connection;
if null
then no Authenticator
will be
usedIOException
- if an error occurs in the transport layerNullPointerException
- if handler
is null