What about apps that are live and need to be updated in real-time? Will there be a way to turn the cache off somehow? My app won't really function well if it's cached, as the info displayed on a user's profile is live data.

I would recommend using client-side script to dynamically return the live data you need.

As far as I know, all apps will get cached and at the moment there aren't any plans to allow a given app to specify whether it is to be cached or not.

Yes! Thank you, thank you, thank you :)

<br/><br/>

Can you confirm whether or not MySpace is also doing makeRequest() caching as described here:

<br/>

<a href="developer.myspace.com/.../a>

Oops, I guess this is one of the few places on MySpace where you aren't supposed to use html :)  The URL in my last post for the makeRequest() caching is:

developer.myspace.com/.../6413.aspx

"I would recommend using client-side script to dynamically return the live data you need."

That's what I'm doing at the moment. So that'll still work properly?

*What's* being cached, exactly? The actual app content (ie. the JavaScript, etc.)?

Also, how come on this blog I can change what it says under "Name (required)", but it just reverts back to my MySpace display name anyways? :P

@ Daaaaaaniel (: ™:

Its the actual app surface and it's contents that are getting cached.

If your app contains client-script to retrieve data realtime, then for the most part that script should still execute the same in the user's browser even if it's a cached version of that script.

@ MarketWall.com:

I am not 100% sure what caching (if any) makeRequest is using. I don't really work in that part of the platform, but I would guess that this won't have any impact on that since we are really only caching the app. surface itself.

I will try to dig up an definitive answer for you.

What about images are they cached?  Our treasure Hunt app dynamically generates an image for every profile view a user makes that has our app installed.  Its essential to its operation (ie: a treasure location with or without a piece of treasure is shown).  Caching that would really break things for our app.

From what I understand of how browsers cache and the change implemented: if your image(s) is/are created with a script, they won't cache. If your content is created with a script, it won't cache.

All that's changing is the page on which the HTML, javascript, etc. is now being cached. So anything static will be cached.

There is no change to the way DataRequest and MakeRequest cache/don't cache information.

Jeremy is spot on.

If you are dynamically adding the content to the page with the script on your app surface then nothing should be different. Static content however, will be cached.

Really this change is geared more towards reducing the page load time for end users and improving performance on the MySpace servers themselves as they render the app surface. All apps should behave as they always have except a little bit more efficiently since static content will be cached.

The real reason for this blog was to make everyone aware of the fact that friends of apps will no longer be able to view apps that are private since we know some developers use that relationship for testing purposes. As the post mentions though, multiple developer support is close and that should replace the need to use friends of apps in the future.