Ok, in the meantime I managed to figure out the problem. My findings are 100% in agreement to Trevor's message as quoted below. Indeed the caching actually occured when loading data with loadVars (using the serialize class from sephiroth.it) and appending a random parameter to the server call (in the AS file) fixed it.
Once I switched to amfphp the caching problem was gone so I did no longer need any parameter to prevent caching. Hope this helps anyone who may be having the same problem in the future. On Dec 27, 6:22 am, "Trevor Burton" <[EMAIL PROTECTED]> wrote:
amfphp calls won't need anything to make them unique - the problem with IE caching xml is well-known and is due to flash caching external data that it calls by the file name it calls it with.... so if you call foo.xml it will cache 'foo.xml' and if you call it again will load the cached version rather than make another call to the server. if you call foo.xml?unique=UNIQUE_ID_HERE then it'll still cache the file but will not locate a file in the cache with the same name on the next request so will request a fresh file from the server.. with amfphp you're effectively making calls to php functions on the server.... so anything that's returned is returned fresh each time... as an amf packet - so the result of your call won't be cached. As an Flash Developer i use both these approaches a lot and simply use a static function to create a unique file name for xml calls and i've never encountered issues with cached amfphp calls before. On 12/27/06, grandpa <[EMAIL PROTECTED]> wrote: > I had SERIOUS problems with IE and a SWF which downloaded data as xml. > I didn't use swfObject but I DID use UFO. I can assure you it didn't > have anything to do with UFO, since I tried to fix this in every way I > could think of. The problem has to do with a setting in IEs prefs... > when caching (something to do with caching, can't remember the pref > name, on my Mac now) is set to "Automatically". This is the default in > Explorer. > Unfortunately, the only way around this problem I found was to append > unique id's to everything. I had to do it to the .swf like so: > "blah.swf?uniqueid="+((new Date).getTime()), to ALL calls to server > scripts that return xml (so this is IN the AS code). I did that in the > same way ( blah.xml.asp?uniqueid="+((new Date).getTime()) ). I didn't > have any control over the server code, so there was nothing I could do > there. > The problem is with IE. Not with anything else. My swf:s, js and html > code worked perfectly before in every other browser EXCEPT IE. > I don't know what advice I could give you regarding amfphp calls... > don't know how to make them unique... but I think that is what you have > to do. > Stupid IE makes caching impossible, which causes more strain on the > server and network.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
