Spring Framwork Web on Servlet Stack v5.3.36 SNAPSHOT
requests on to the WebSocket server. Likewise, if the application runs in a cloud environment, check the instructions of the cloud provider related to WebSocket support. 4.1.1. HTTP Versus WebSocket Even and can be useful (for example, in a cloud environment where the actual host to which the TCP connection is established differs from the host that provides the cloud-based STOMP service). 4.4.11. Dots infrastructure 245 components automatically gather statistics and counters that provide important insight into the internal state of the application. The configuration also declares a bean of0 码力 | 259 页 | 3.58 MB | 1 年前3Spring Framework Reference Documentation 4.3.26.RELEASE
and not per VM. Refer to the section called “Spring configuration” in the AOP chapter for more insight regarding the LoadTimeWeaver implementations and their setup, either generic or customized to various with the 2.0.x generation of Reactor. Therefore it is not supported in combination with the spring- cloud-stream-reactive module which requires Reactor 3.x. Spring Framework 5 relies on Reactor 3 and Reactor and may be useful for example in a cloud environment where the actual host to which the TCP connection is established is different from the host providing the cloud-based STOMP service. Dot as Separator0 码力 | 1323 页 | 4.08 MB | 1 年前3Spring Framework Reference Documentation 4.3.26.RELEASE
and not per VM. Refer to the section called “Spring configuration” in the AOP chapter for more insight regarding the LoadTimeWeaver implementations and their setup, either generic or customized to various with the 2.0.x generation of Reactor. Therefore it is not supported in combination with the spring-cloud-stream- reactive module which requires Reactor 3.x. Spring Framework 5 relies on Reactor 3 and Reactor and may be useful for example in a cloud environment where the actual host to which the TCP connection is established is different from the host providing the cloud-based STOMP service. Dot as Separator0 码力 | 916 页 | 5.52 MB | 1 年前3Spring Framework Reference Documentation v4.3.2
and not per VM. Refer to the section called “Spring configuration” in the AOP chapter for more insight regarding the LoadTimeWeaver implementations and their setup, either generic or customized to various and may be useful for example in a cloud environment where the actual host to which the TCP connection is established is different from the host providing the cloud-based STOMP service. Using Dot as Separator > key infrastructure components automatically gather stats and counters that provide important insight into the internal state of the application. The configuration also declares a bean of type WebSo0 码力 | 1311 页 | 4.07 MB | 1 年前3Spring Framework Reference Documentation v4.3.2
and not per VM. Refer to the section called “Spring configuration” in the AOP chapter for more insight regarding the LoadTimeWeaver implementations and their setup, either generic or customized to various and may be useful for example in a cloud environment where the actual host to which the TCP connection is established is different from the host providing the cloud-based STOMP service. Using Dot as Separator r> key infrastructure components automatically gather stats and counters that provide important insight into the internal state of the application. The configuration also declares a bean of type WebSo0 码力 | 907 页 | 5.46 MB | 1 年前3Apache ActiveMQ Artemis 2.26.0 User Manual
approaches to messaging are showing a lot interest recently. It seems plausible that API standards for cloud computing may converge on a REST style set of interfaces and consequently a REST messaging approach loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience0 码力 | 487 页 | 6.28 MB | 1 年前3ActiveMQ Artemis 2.27.1 Documentation
loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. securityEnabled=false acceptorConfigurations.tcp.factoryClassName=org.apache.activemq.artemis0 码力 | 414 页 | 6.20 MB | 1 年前3Apache ActiveMQ Artemis 2.30.0 User Manual
loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the0 码力 | 500 页 | 6.37 MB | 1 年前3Apache ActiveMQ Artemis 2.28.0 User Manual
loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively Clusters 362 frequently. When scaling up a cluster suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the0 码力 | 494 页 | 6.33 MB | 1 年前3Apache ActiveMQ Artemis 2.29.0 User Manual
loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the0 码力 | 499 页 | 6.37 MB | 1 年前3
共 299 条
- 1
- 2
- 3
- 4
- 5
- 6
- 30