Skip to main content

JavaScript: asynchronous function that resumes to synchronous



I have a large script that is very synchronous.





1) it runs a function like this:







var result = doSomethingSynchronous(myVar);

if (result === 'something') {

doSomethingElse();

}







the doSomethingSynchronous function has a for loop that returns a value on a if statement:







var i = 0; le = someVariable.length;

for (; i < len; i++) {

if (someVariable[i] === 'aString') {

return true;

} else {

doSomethingElse();

}

}







Because the for loop and the processing can be intense, I've replaced the for loop with an iterative queue processing function that runs itself asynchronously using setTimeout after shifting one element from the array. Once it runs asynchronously of course it doesn't return the value and assigns it to the 'result' variable in the first snippet synchronously, and the if statement there always fails. My question is, is there a way to keep this part synchronous? Have the value be assigned to result before the script goes on to the next line? Or do I necessary have to use the observer/mediator pattern or similar to notify that the asynchronous function is completed?





Alternatively I could use a callback, but the actual real code is longer than this one and all depend on synchronicity. So switching var result = doSomethingSynchronous() to asynchronous would have a domino effect on the rest of the synchronous scripts, correct? :-) This sounds like a difficult and error-prone conversion, so I thought I'd ask for advice.





Thanks!


Comments

  1. In order to assign the result to a value, you would need to pass through a callback and call that instead of returning a value, whether or not you're deferring functionality to a timer or not.

    function doSomething(someVariable, callback){
    var i = 0; le = someVariable.length;
    for (; i < len; i++) {
    if (someVariable[i] === 'aString') {
    callback && callback(true);
    break;
    } else {
    setTimeout(function(){ deferredSomething(callback); }, 10);
    }
    }
    }

    function deferredSomething(callback){
    /* code.. */
    callback && callback('something');
    }

    doSomething(myVar, function(result){
    if (result === 'something') {
    doSomethingElse();
    }
    });


    I'll also mention that if you are doing something intense, you should definitely look at web workers so you can offload to a background thread, especially if you're working with just a FireFox add-on. https://developer.mozilla.org/En/Using_web_workers

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex