From 75401be4527a7b77d8dbbf26f60d61ec3bfdb92d Mon Sep 17 00:00:00 2001 From: "av%netscape.com" Date: Wed, 6 Mar 2002 03:53:40 +0000 Subject: [PATCH] Readme file for the plugin sample code, not part of the build git-svn-id: svn://10.0.0.236/trunk@115925 18797224-902f-48f8-a5cc-f745e15eee43 --- .../samples/npthread/windows/readme.txt | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 mozilla/modules/plugin/samples/npthread/windows/readme.txt diff --git a/mozilla/modules/plugin/samples/npthread/windows/readme.txt b/mozilla/modules/plugin/samples/npthread/windows/readme.txt new file mode 100644 index 00000000000..ba7a5516515 --- /dev/null +++ b/mozilla/modules/plugin/samples/npthread/windows/readme.txt @@ -0,0 +1,24 @@ +03-05-2002 + +This sample is an attempt to write a wrapper plugin which would run the +real plugin in a separate thread. The current code is just a first prototype +version aimed to determine the very possibility of such thing. It is not +designed to handle more than one instance of one plugin. Another limitations +are: it only relays browser-to-plugin calls in thread event based matter +(calls from the plugin to the browser are just made directly by function +pointer; it does not implement notifications back from the plugin thread +to the calling thread, so it simply waits before each NPP_* call until +the plugin thread is done with the previous NPP_* call. + +The wrapper tested with Basic plugin sample from the plugin +SDK, so some common plugin crashes can be modelled. Work is still +required to make it functional with more complicated plugins +like Flash. + +Steps to see it in action: + + -- place the wrapper plugin (npthread.dll) in the plugins folder + -- remove npnul32.dll from the plugins folder + -- rename the plugin you want to run in a separate thread adding + two zeroes at the beginnig (ren npbasic.dll 00npbasic.dll) + -- run test case for the plugin in question