ClientChannel.SimpleRegistrationHandler
@Deprecated
protected static interface ClientChannel.RegistrationHandler
RegistrationHandler
when
connection is opened.
Channel will call getRegistrationMessage()
first
and send this message to server. Then the channel will
waitResponse for an answer from server and while
isRegistrationComplete()
returns false
the process is repeated. So, in complex registration scenarios
your RegistrationHandler probably has to be "stateful" and
handle order of messages supplied to channel.
Usually there is only one registration message, so you can use
SimpleRegistrationHandler to perform such simple registration.Modifier and Type | Method | Description |
---|---|---|
Message |
getRegistrationMessage() |
Deprecated.
|
boolean |
handleResponse(Message response) |
Deprecated.
|
boolean |
isRegistrationComplete() |
Deprecated.
|
Message getRegistrationMessage()
boolean handleResponse(Message response) throws ProtocolException
ProtocolException
boolean isRegistrationComplete()
Send comments on this topicTechpubs.webadmin@genesys.com.
Document version: 9.0.006.00
Copyright © 2006–2019 Genesys Telecommunications Laboratories, Inc. All rights reserved.