3 ms·

Hi Mattkol, Is there a reason why you chose to use Ajax instead of WebSockets which has much lower latency and overhead? Not backward compatibility I hope! The

Hi Mattkol, Is there a reason why you chose to use Ajax instead of WebSockets which has much lower latency and overhead? Not backward compatibility I hope! The spec was finalized and implemented ages ago.

mattkol 8y ago
Actually I am currently looking at websocket, but not for the same reason you raised. I was looking at extending for real-time apps. However ... Ajax is one of the options of IPC, and this is common to both CefGlue and CefSharp implementations. The options are: 1. Ajax HTTP/XHR (Xilium.CefGlue, CefSharp) 2..NET/Javascript integration (CefSharp) 3. Generic Message Routing (Xilium.CefGlue) I see 2 and 3 as the common usage for the CEF .NET community. Ajax may see less usage because it's use can result in other issues -- like cross-origin error and may be more complex for some people. Like I said, I have just started looking into WebSocket and may soon be implemented for CefGlue apps.