we know there small overhead firebreath 2.0 plugins in chrome because framework creates thin ppapi executable run plugin within.
however, mozilla , safari firebreath plugin add overhead compared bare npapi plugin?
in our case porting stockfish chess engine plugin c++ code cpu intensive , small overhead significant.
firebreath 2.0 not use ppapi -- ppapi not viable solution third party plugins because unless used native client plugin not usable unless enabled command line parameter each time chrome launched.
firebreath 2.0 uses native messaging , plugin loaded in native message host executable; there no overhead far running c++, interface communicate browser uses json , string-based, there absolutely overhead there.
basically depends on concern -- if need super high speed communication between browser , firebreath plugin you'll need performance testing see if it's enough or not. if need c++ code fast before no problems -- it's native code, it's every bit fast. overhead come whenever communicate browser.
Comments
Post a Comment