Hi,
Take a look at- 
http://code.google.com/p/opensocial-resources/wiki/OpenSocialBestPracticesTo 
minimize make request calls use the app's persistant data storage as much as 
possible.Thanks ~Aakashhttp://aakash-bapna.blogspot.com 

> Date: Mon, 16 Jun 2008 21:22:57 -0700> Subject: [OpenSocial] OpenSocial 
> Coding Practices> From: [EMAIL PROTECTED]> To: 
> [email protected]> > > > Hi all,> > Of late, I have started 
> building large scale applications using> Opensocial API, and I notice that my 
> code involves lots of makeRequest> calls and many callback functions. Using 
> all this javascript in a> single xml file might not be the best way to do it. 
> Are there any> guidelines on :> > 1) how to keep the code neat and 
> good-looking> 2) ways to minimize multiple makeRequest calls> > Also, I am 
> not sure whether it is a good practice to break up my> javascript into 
> multiple smaller files. This will improve code> readability, but I am afraid 
> that it might increase the latency> because the application now has to access 
> more number of files. Please> provide me your suggestions and views on this.> 
> > > Thank you,> Prafulla> > > 
> _________________________________________________________________
Introducing Live Search cashback .  It's search that pays you back!
http://search.live.com/cashback/?&pkw=form=MIJAAF/publ=HMTGL/crea=introsrchcashback
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to