public class SenderConfiguration extends Object
SenderConfigurationProvider.SenderConfigurationProvider| Constructor and Description |
|---|
SenderConfiguration() |
SenderConfiguration(int batchesToLoad,
int batchSize)
Creates a new configuration with the configuration values provided
|
| Modifier and Type | Method and Description |
|---|---|
int |
batchesToLoad()
Specifies how many batches should be loaded in one token-loading transaction.
|
int |
batchSize()
Batch size specifies how many devices will be loaded and delivered in one batch.
|
int |
tokensToLoad()
This is a derived property, computed as a product of
batchesToLoad() and batchSize(). |
public SenderConfiguration()
public SenderConfiguration(int batchesToLoad,
int batchSize)
batchesToLoad - specifies how many batches should be loaded in one transaction (see batchesToLoad()batchSize - specifies how many devices will be loaded and delivered in one batch (see batchSize()public int batchesToLoad()
batchesToLoad() in one transaction.
This avoids long transactions and enables fail-over procedures.public int batchSize()
PushNotificationSender implementation.
Smaller batches allows better fail-over, but can be unfriendly to the Push Network, since it has to allow UPS establish more connections.
Larger batches allows for more effective communication, however you must be aware of memory limits configured for UPS message queues.
One device token theoretically requires 2 * (upper-bound limit of its length) bytes of memory.
The minimum or maximum lengths of specific push networks are partially listed in DeviceTokenValidator.public int tokensToLoad()
batchesToLoad() and batchSize().
It configures how many tokens will be loaded in one token-loading transaction.batchesToLoad() and batchSize().Copyright © 2017 JBoss by Red Hat. All rights reserved.