emitter.complete() While SSE is the main option for streaming into browsers, note that Internet Explorer does not support Server-Sent Events. Consider using Spring’s WebSocket messaging with SockJS fallback 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 options — for example, to specify which transports to include. 211 4.3.3. IE 8 and 9 Internet Explorer 8 and 9 remain in use. They are a key reason for having SockJS. This section covers important considerations

WebSocket emulation) for use in browsers that don’t yet support the WebSocket protocol (e.g. Internet Explorer < 10). A new spring-messaging module adds support for STOMP as the WebSocket sub- protocol to use Spring MVC and requires simply returning a value of type SseEmitter. Note however that Internet Explorer does not support Server-Sent Events and that for more advanced web application messaging scenarios SockJS-style WebSocket emulation falling back to a very wide range of browsers (including Internet Explorer) and also higher-level messaging patterns for interacting with clients through a publish-subscribe

WebSocket emulation) for use in browsers that don’t yet support the WebSocket protocol (e.g. Internet Explorer < 10). Spring Framework Reference Documentation 4.3.26.RELEASE Spring Framework 22 A new spring-messaging Spring MVC and requires simply returning a value of type SseEmitter. Note however that Internet Explorer does not support Server-Sent Events and that for more advanced web application messaging scenarios SockJS-style WebSocket emulation falling back to a very wide range of browsers (including Internet Explorer) and also higher- level messaging patterns for interacting with clients through a publish-subscribe

WebSocket emulation) for use in browsers that don’t yet support the WebSocket protocol (e.g. Internet Explorer < 10). A new spring-messaging module adds support for STOMP as the WebSocket sub- protocol to use Spring MVC and requires simply returning a value of type SseEmitter. Note however that Internet Explorer does not support Server-Sent Events and that for more advanced web application messaging scenarios SockJS-style WebSocket emulation falling back to a very wide range of browsers (including Internet Explorer) and also higher-level messaging patterns for interacting with clients through a publish-subscribe

251 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 6.1. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 6.1.1. Cloud Foundry . . . . . . . . .

253 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.1. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.1.1. Cloud Foundry . . . . . . . . .

253 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.2. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 6.2.1. Cloud Foundry. . . . . . . . .

255 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 6.2. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 6.2.1. Cloud Foundry. . . . . . . . .

253 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.2. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 6.2.1. Cloud Foundry. . . . . . . . .

254 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 6.2. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 6.2.1. Cloud Foundry. . . . . . . . .