Quote from: 1bitc0inplz on May 21, 2011, 12:19:15 PM

Just a quick update...

We changed the default script that is generate for you to have the forceUIThread parameter set to true. This will force the script to be very, very, nice. You can still overwrite that setting by explicitly setting it to false, doing so will increase your hash rate at the risk of higher CPU usage for your website visitors.

As promised, here is a complete list of parameters that can be passed into the engine:

clientId
delay
forceUIThread
autoStart
workerTimeout

clientId - this is your unique identifier. Do not change, unless of course you want your shares going to someone else Cheesy

delay - this is the delay, in milliseconds that the UI thread waits between every 100 hashes. This setting does not control web workers. Lowering this value too much could result in browsers displaying the "we've detecting that this script has locked up" warnings. The default is 30 ms.
forceUIThread - some browsers don't support web workers (IE), in those cases this setting is meaningless. For browser that support web workers, this forces them *not* to use them, and instead calculate hashes in the UI thread at a much slower, and less CPU intensive, rate.
autoStart - don't use this yet. Right now the jsMiner auto starts. You could set it to false. However, since the jsMiner is running in an iframe you would have no way of starting it... we will work on getting this better exposed.
workerTimeout - this effects all browsers. This is the length of time (in seconds) that a get work request is good for. The default is 30 seconds. Increasing this value decreases network request but increases the likelihood of stale shares.

And example of what you're modified script tag would look like with some of these parameters is:

Code:

Why dont you show the code on the website when we login?