Used in: proxy-scheme.
The acceptor-config element specifies the configuration info for a protocol-specific connection acceptor used by a proxy service to enable Coherence*Extend clients to connect to the cluster and use the services offered by the cluster without having to join the cluster.
The acceptor-config element must contain exactly one protocol-specific connection acceptor configuration element (either jms-acceptor or tcp-acceptor).
The following table describes the elements you can define within the acceptor-config element.
|<jms-acceptor>||Optional||Specifies the configuration info for a connection acceptor that enables Coherence*Extend clients to connect to the cluster over JMS.|
|<tcp-acceptor>||Optional||Specifies the configuration info for a connectio330cceptor that enables Coherence*Extend clients to connect to the cluster over TCP/IP.|
|<outgoing-message-handler>||Optional||Specifies the configuration info used by the connection acceptor to detect dropped client-to-cluster connections.|
|<use-filters>||Optional||Contains the list of filter
names to be used by this connection acceptor.
For example, specifying use-filter as follows
will activate gzip compression for all network messages, which can help substantially with WAN and low-bandwidth networks.
|<serializer>||Optional||Specifies the class configuration info for a Serializer implementation used by the connection acceptor to serialize and deserialize user types.
For example, the following configures a ConfigurablePofContext that uses the my-pof-types.xml POF type configuration file to deserialize user types to and from a POF stream: