blob: 4fa9a426ad0eb8d3fbe66934a542e4e2d2518659 [file] [log] [blame]
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Client-Level-Data</title>
</head>
<body>
<p>Both BlazeDS and LiveCycle Data Services provide data throttling features that give you control over aspects of the server’s underlying messaging system. You use data throttling to limit the number of server-to-client and client-to-server messages that a Message Service or Data Management Service destination can process per second. You can also set absolute limits for the number of client-to-server and server-to-client messages allowed per second. Without data throttling, the server pushes messages to clients without any indication on how fast the clients are processing messages. Similarly, a high number of messages from Flex clients can overwhelm a server. Throttling is useful when the server could overwhelm slow clients with a high number of messages that they cannot process or the server could be overwhelmed with messages from clients. </p>
<p>For server-to-client messages in LiveCycle Data Services, you can use adaptive throttling to message frequency limits based on the message processing rates of clients. You can also set policies that determine what happens to messages that exceed the specified maximum message limits. Note: In addition to these standard throttling features, a set of advanced capabilities are available in LiveCycle Data Service only. </p>
<p>For more information, visit: http://help.adobe.com/en_US/LiveCycleDataServicesES/3.1/Developing/WS3a1a89e415cd1e5d-5898af47122bdca6709-8000Update.html </p>
</body>
</html>