Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Chapter 4: Channels and endpoints > Configuring channels with servlet-based end... - Pg. 45

BLAZEDS 43 BlazeDS Developer Guide Configuring channels with servlet-based endpoints The servlet-based endpoints are part of both BlazeDS and LiveCycle Data Services ES. Simple channels and endpoints The AMFEndpoint and HTTPEndpoint are simple servlet-based endpoints. You generally use channels with these endpoints without client polling for RPC service components, which require simple call and response communi- cation with a destination. When working with the Messaging Service, you can use these channels with client polling to constantly poll the destination on the server for new messages, or with long polling to provide near real-time messaging when using a streaming channel is not an option in your network environment. Property polling-enabled polling-interval-millis Description Optional channel property. Default value is false. Optional channel property. Default value is 3000. This parameter specifies the number of milliseconds the client waits before polling the server again. When polling-interval-millis is 0, the client polls as soon as it receives a response from the server with no delay. Optional endpoint property. Default value is 0 . This parameter specifies the number of milliseconds the server poll response thread waits for new messages to arrive when the server has no messages for the client at the time of poll request handling. For this setting to take effect, you must use a nonzero value for the max-waiting-poll-requests property. A value of 0 means that server does not wait for new messages for the client and returns an empty acknowledgment as usual. A value of -1 means that server waits indefinitely until new messages arrive for the client before responding to the client poll request. The recommended value is 60000 milliseconds (one minute). wait-interval-millis client-wait-interval-millis Optional channel property. Default value is 0 . Specifies the number of milliseconds the client will wait after it receives a poll response from the server that involved a server wait. A value of 0 means the client uses its configured polling-interval-millis value to determine the wait until its next poll. Otherwise, this value overrides the default polling interval of the client. Setting this value to 1 allows clients that poll the server with wait to poll immediately upon receiving a poll response, providing a real-time message stream from the server to the client. Any clients that poll the server and are not serviced with a server wait use the polling-interval-millis value. Optional endpoint property. Default value is 0 . Specifies the maximum number of server poll response threads that can be in wait state. When this limit is reached, the subsequent poll requests are treated as having zero wait-interval-millis . Optional endpoint property. Enable to support piggybacking of queued messaging and data management subscription data along with responses to any messages the client sends to the server over this channel. Optional channel property. Default value is false . Setting to true causes clients to automatically attempt to reauthenticate themselves with the server when they send a message that fails because credentials have been reset due to server session timeout. The failed messages are resent after reauthentication, making the session timeout transparent to the client with respect to authentication. max-waiting-poll-requests piggybacking-enabled login-after-disconnect