зеркало из https://github.com/mozilla/gecko-dev.git
635fc0e1ae
After data delivery for a request has been retargeted, there's no reliable way to get the appropriate event target to re-dispatch data events after asynchronous processing. While it's technically possible to retrieve the current thread from OnDataAvailable callbacks and re-use that for later dispatch, that approach has some issues: 1) It's not currently possible to reliably map the current thread to the thread pool that owns it. That means that if data delivery is being targetted to a thread pool, attempts to redispatch events to the previous delivery thread might lead to long delays when one thread in a pool is blocked. 2) If a filter wishes to dispatch data events to the wrapped listeners before it's recieved any data (as extensions StreamFilters sometimes do), there's no way to determine the proper event target without waiting for initial data to be received. Simply returning the correct event target from the request solves both of these problems. MozReview-Commit-ID: CJxq7O4399R --HG-- extra : rebase_source : db2f659ecad16daafdbcc108d7b1a51ea1af31f9 |
||
|---|---|---|
| .. | ||
| BaseWebSocketChannel.cpp | ||
| BaseWebSocketChannel.h | ||
| IPCTransportProvider.cpp | ||
| IPCTransportProvider.h | ||
| PTransportProvider.ipdl | ||
| PWebSocket.ipdl | ||
| PWebSocketEventListener.ipdl | ||
| WebSocketChannel.cpp | ||
| WebSocketChannel.h | ||
| WebSocketChannelChild.cpp | ||
| WebSocketChannelChild.h | ||
| WebSocketChannelParent.cpp | ||
| WebSocketChannelParent.h | ||
| WebSocketEventListenerChild.cpp | ||
| WebSocketEventListenerChild.h | ||
| WebSocketEventListenerParent.cpp | ||
| WebSocketEventListenerParent.h | ||
| WebSocketEventService.cpp | ||
| WebSocketEventService.h | ||
| WebSocketFrame.cpp | ||
| WebSocketFrame.h | ||
| WebSocketLog.h | ||
| moz.build | ||
| nsITransportProvider.idl | ||
| nsIWebSocketChannel.idl | ||
| nsIWebSocketEventService.idl | ||
| nsIWebSocketListener.idl | ||