Hi Rohit, I guess you are right. Trying to use these functions synchronously only makes the code messy. I have altered my design and am trying to minimize the number of makeRequest calls also.
Thanks a lot!, Prafulla On Jun 18, 1:33 pm, "Rohit Ghatol (Google)" <[EMAIL PROTECTED]> wrote: > Hi Prafulla, > If you absolutely must make use of a synchronous call, that is not > considered a good design practice. I would urge, that if it is > possible to change your design to make use of asynchronous calls, > there is nothing better than that. > It keeps the user experience good and is a good design to follow for > browser based apps. > > Yes we do use asynchronous calls at places like DataRequest.send(). > And this is a very common api. > > Let me know what you think. > Regards, > Rohit > > On Jun 18, 11:15 am, prafulla <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I have a couple of problems. > > > 1) Is there any way to stop the execution of javascript until we get > > the response from makeRequest ? I am modifying some global variables > > in the callback function of makeRequest. So, I need to wait until the > > response is complete. For normal AJAX, there is a parameter which > > allows us to use ajax in a synchronous manner. How can it be done for > > gadgets.io.makeRequest ? > > > 2) Also, are there any other asynchronous functions in the opensocial > > API apart from the makeRequest function ? If yes, how do I use them > > synchronously ? > > > Thank you, > > Prafulla > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" 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/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
