https://sourceforge.net/p/chromedevtools/wiki/WipBackends/Recent changes to WipBackendsenSat, 25 Apr 2015 13:43:47 -0000https://sourceforge.net/p/chromedevtools/wiki/WipBackends/<div class="markdown_content"><h1 id="introduction">Introduction</h1> <p>WIP Backends is a design artifact of <a class="" href="/p/chromedevtools/wiki/WIP">WebKit Remote Debugging Protocol</a> client implementation. It allows to have several different protocol implementations behind the single SDK interface. Technically WIP backend is a sub-library that should be used together with the main SDK library. There are several of them. </p> <p>This is how Java SDK tolerates the fact that different versions of Google Chrome/Chromium simultaneously available may have incompatible protocols. </p> <p>WIP Backend is currently a user-visible detail. This means that it's a user responsibility to correctly select a proper WIP Backend before attaching from debugger. Each backend is presented in <a class="" href="/p/chromedevtools/wiki/EclipseDebugger">Debugger</a> UI in <code>Debug Configurations</code> dialog with a small declaration of compatible browser versions. </p> <p>The exact set of backends change from release to release. That's why they are normally listed in release notes. </p> <p>WIP Backends are deployed as a separate Eclipse feature "ChromeDevTools SDK WIP Backends". </p></div>AnonymousSat, 25 Apr 2015 13:43:47 -0000https://sourceforge.net90e11227ae7f212393be374cda369db657c8cd30