Standardize WebSocket integration with f:websocket #1396
Comments
Reported by @edburns |
@BalusC said: As discussed, I dropped SSE support as it isn't standardized and has less browser support (no Microsoft IE/Edge), while WS is standardized, even in Java EE (JSR356), and has better browser support and is more efficient (no persistent open connection). |
@BalusC said: |
@BalusC said: |
@BalusC said: |
@BalusC said: |
@BalusC said: |
@BalusC said: |
File: JAVASERVERFACES_SPEC_PUBLIC-1396.patch |
@BalusC said: https://java.net/projects/mojarra/sources/git/revision/598058f425f8894683f1d68796b0474e54cfea9e |
@BalusC said: |
@BalusC said: Commited improvement as to handling of jsf.js script (refactored utility from AjaxHandler into RenderKitUtils so it can be reused by WebsocketHandler's WebsocketFacesListener). Initial implementation broke state saving. https://java.net/projects/mojarra/sources/git/revision/ac4253639ed23eace38451fff3c33c6e9780be2b |
@BalusC said: https://java.net/projects/mojarra/sources/git/revision/9c65817db3c9e80421911692e83319ad8c97ac1e |
@BalusC said: |
@BalusC said: 1. f:websocket needs to be an UIComponent implementing ClientBehaviorHolder |
@BalusC said: |
@edburns said: 5ff3e2b |
@edburns said: |
@BalusC said: |
@BalusC said:
<f:websocket> and jsf.push.init() have been modified to drop port attribute and argument. |
Marked as fixed on Friday, December 23rd 2016, 10:38:07 am |
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-1396 |
Standardize WebSocket integration with f:websocket
The text was updated successfully, but these errors were encountered: