My understanding is (unconfirmed, though) that if you use HTTPService and request the same URL twice, and the server has set the cache headers appropriately it should be served out of cache on the second hit (at least on Windows, where the player uses WinInet). You can test this pretty easily with a URL that points to a static XML file and watch the traffic using a network sniffer. I'd guess that you'd see a HTTP GET on the first hit, possibly followed by a HTTP HEAD on the second (or nothing), depending on the settings in the IE cache setup.
-Roger Roger Gonzalez mailto:[EMAIL PROTECTED] > -----Original Message----- > From: sbyrne_dorado [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 06, 2004 1:57 PM > To: [email protected] > Subject: [flexcoders] Re: "Almost" read-only client side cache > > Hi Roger, > I just wanted clarification on point 1: are you saying that if I had > Flex download the XML that the browser would cache it, or are you > saying that I need to arrange for the browser, outside of Flex, to > download the XML file, and somehow then let Flex discover the file's > content, or have it somehow reach into the browser's object model to > retrieve that content? > > --- In [email protected], Roger Gonzalez > <[EMAIL PROTECTED]> wrote: > > You have a few options. > > > > 1) Encode your state in XML, and download it separately. If things > are set > > up correctly, the XML file will be stored in the browser cache. > > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Yahoo! Domains - Claim yours for only $14.70 > http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/nhFolB/TM > -------------------------------------------------------------- > -------~-> > > > Yahoo! Groups Links > > > > >
