order-of-execution

Okay, so I appreciate that Javascript is not C# or PHP, but I keep coming back to an issue in Javascript - not with JS itself but my use of it. I have a function: function updateStatuses(){ showLoader() //show the 'loader.gif' in the UI updateStatus('cron1'); //performs an ajax request to get the status of something updateStatus('cron2'); updateStatus('cron3'); updateStatus('cronEmail'); updateStatus('cronHourly'); updateStatus('cronDaily'); hideLoader(); //hide the 'loader.gif' in the UI } Thing is, owing to Javascript's burning desire to jump ahead in the code, the loader never appears

If we define webapp specific servlet filters in WAR's own web.xml , then the order of execution of the filters will be the same as the order in which they are defined in the web.xml . But, if we define those filters using @WebFilter annotation, what is the order of execution of filters, and how can we determine the order of execution? BalusC You can indeed not define the filter execution order using @WebFilter annotation. However, to minimize the web.xml usage, it's sufficient to annotate all filters with just a filterName so that you don't need the <filter> definition, but just a <filter

A little question about creating objects. Say I have these two classes: struct A{ A(){cout << "A() C-tor" << endl;} ~A(){cout << "~A() D-tor" << endl;} }; struct B : public A{ B(){cout << "B() C-tor" << endl;} ~B(){cout << "~B() D-tor" << endl;} A a; }; and in main I create an instance of B : int main(){ B b; } Note that B derives from A and also has a field of type A . I am trying to figure out the rules. I know that when constructing an object first calls its parent constructor, and vice versa when destructing. What about fields ( A a; in this case)? When B is created, when will it call A 's