The following properties apply to the TCP Lateral Cache plugin.
Property | Description | Required | Default Value |
---|---|---|---|
TcpServers | This is the list of servers this cache should try to connect to. With UDP discovery this is not necessary. | N | none |
TcpListenerPort | This is the port this cache should listen on. | Y | n/a |
AllowGet | Should this cache be allowed to get from other laterals. False means that it can only put, i.e. send updates and remove requests to other laterals. Lateral gets are not recommended for performance reasons. This used to be controlled by the attribute PutOnlyMode. | N | true |
Receive | Should this cache receive or only send to other laterals. You may want to set receive to false if you just need to broadcast to other caches. If you have a feed data parser, that doesn't need to receive updates, but you do want it to send invalidation messages, then you would set receive to false. If receive is false, teh discovery service, if enabled, will only listen. | N | true |
IssueRemoveOnPut | If this is set to true, then the lateral client will send a remove command rather than a put command to any registered listeners. | N | false |
FilterRemoveByHashCode | If this is true, and IssueRemoveOnPut is true, the client will include the hashCode of the element to remove. If it is also true on the receiving end, the receiver will check to see if the element exists. If the element exists, and the hashCodes are the same, the item will not be removed. | N | false |
UdpDiscoveryAddr | The address the UDP discovery process should broadcast messages to. | N | 228.5.6.7 |
UdpDiscoveryPort | The port the UDP discovery process should send messages to. | N | 6789 |
UdpDiscoveryEnabled | Whether or not the UDP discovery service should be used to locate other lateral caches. | N | true |