Subject: Restore Vision loss (14 days)

From: Vision Restored <[email-masked]>
Date: Thu, 12 Jun 2014 11:28:05 -0700

The Eyecare industry is FURIOUS at this woman who has stumbled upon a ground-breaking 
program to restore anybody's 20/20 vision in as little as 2 weeks!

This scientifically proven program to Vision without glasses can help cure
Myopia, Hyperopia, Presbyopia and many other visual problems.

** Watch the shocking presentation -> http://www.vegarc.com/vision/psa/video.index

They are desperately trying to take down this video so view it while you can. 
I can't say it will be up for much longer...

See Scientific Explanation: http://www.vegarc.com/vision/psa/video.index

We hope that you found this vision alertful useful.
f you would like t stop further notifications - write "stop" to Member Update Systems
9167 ROAD 177_Oakwood, OH four five eight seven three or http://www.vegarc.com/03fj.sfvt

 don't understand the issue with the focus/blur behaviour -- to me that seems totally expected. When something is focused or blurred I want to know ASAP. But, I do understand why you mentioned it -- it is relevant to the topic :)   James Apr 29 '10 at 2:29 
10	  	
@J-P: Personally I don't want to know straight away because it means I have to be careful that my code is re-entrant, that calling my blur code won't affect state that some outer code is relying on. There are too many cases where blurring is an unexpected side-effect to necessarily catch every one. And unfortunately even if you do want it, it's not reliable! IE fires blur after your code returns control to the browser.   bobince Apr 29 avascript is single threaded. Halting your execution on alert() doesn't mean the event thread stops pumping events. Just means your script is sleeping while the alert is on the screen, but it has to keep pumping events in order to draw the screen. While an alert is up the event pump is running which means it's entirely correct to keep sending out events. At best this demonstrates a cooperative threading that's can happen in javascript, but all of this behavior could be explained by a function simply appending an event to the event pump to be processed 
 at a later point vs. doing it now.But, remember cooperative threading is still single threaded. Two things can't happen simultaneously which is what multi-threading allows and injects non-determinism. All of what was described is deterministic, and it's a good reminder about these types of issues. Good job on the  is right: JavaScript is single threaded. This is not an example of multithreading, but rather synchronous message dispatch in a single thread. Yes, it's possible to pause the stack and have event dispatch continue (e.g. alert()), but the kinds of access problems that occur in true multithreaded environments simply can't happen; for example, you will never have a variable change values on you between a test and an immediately subsequent assignment, because your thread cannot be arbitrarily interrupted. I fear that this response is only going to cause confusion.  see the discussion of the watchdog in modern browsers, which can indeed arbitrarily interrupt your thread of exec
 ution. If you have a long-running script and you are unlucky it is eminently possible to have a variable change between being tested and subsequent assignment. Do you have a link to that discussion? I should probably clarify that while it is possible to have the JavaScript thread interrupted (obviously the host application can have multiple threads) the question is whether one thread running JavaScript can be interrupted by another thread running JavaScript against the same global context. It might be possible to build an application that does this by subverting the intent of the JavaScript engine, but this example does not illustrate that.   Kris Giesing Jul 21 '11 at 19:48 
1	  	
This description isn't really one of a multithreadded environment, though, where execution happens literally in parallel. Rather, it's simply evidence that any point you call a blocking function which waits for user input, the browser re-enters its event loop.