I've skim through your messages, and i think could solve your problem using callbacks. You can not play the speed loading game as you can't predict internet speeds nor browser's speeds. With callbacks you can control that a task/function runs only and only after another task/function finish doing its thing. Kind of having like a dominoes effect on your application, one function leading to another.
Sent from my iPhone On Mar 5, 2012, at 4:27 PM, UTAN <[email protected]> wrote: > I've tried to pass the id of the user logged in to JavaScript then to > Ape and make the query so I could run the query even faster.. but no > it didn't work... > > And I guess I am the only one that had had this issue.. > > What gets me mad is same version of Ape same server OS in my test bed > works fine but in production it doesn't. > > > -- > You received this message because you are subscribed to the Google > Groups "APE Project" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/ape-project?hl=en > --- > APE Project (Ajax Push Engine) > Official website : http://www.ape-project.org/ > Git Hub : http://github.com/APE-Project/ -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
