All I know is that "URLRequest.useCache" is native property, and it would be 
very strange if C++ implementation internally added some random string to 
request instead of working with platform specific API or implementing own from 
scratch.

--
Thanks,
Vadim.

  ----- Original Message ----- 
  From: Kevin 
  To: [email protected] 
  Sent: Monday, December 17, 2007 3:37 PM
  Subject: Re: [flexcoders] Beta 2 bug? "useCache" not available in URLRequest


  ah, thanks for the clarification.  somehow I missed that part about AIR.  It 
seem like it would not be too hard (or a security problem) to build that 
functionality into the regular version.  I implement the same functionality by 
just appending a random string onto the URL when I want to force a load from 
the server.  Somewhat of a hack, but it works...  I figured they had done a 
similar thing, but just built it into the URLRequest object.



  Thanks, kevin





  On Dec 15, 2007, at 8:07 AM, Vadim Melnik wrote:




    Hi Kevin,

    Didn't work with "useCache" before, but just looked at Flex 3 Beta 3:

    "useCache",  "userAgent" and brothers only available in URLRequest coming 
with AIR Beta 3 runtime (airglobal.swc),
    But standard Flex Beta 3 runtime (playerglobal.swc) contains old restricted 
version without advanced functionality. Probably this is done due to security 
reasons...

    --
    Thanks,
    Vadim Melnik,
    http://www.docsultant.com/



      ----- Original Message -----
      From: Kevin
      To: [email protected]
      Sent: Thursday, December 13, 2007 7:54 PM
      Subject: [flexcoders] Beta 2 bug? "useCache" not available in URLRequest


      The docs say there is a new public property 'useCache' that I can set 
      to force a reload from the server of the URL. Yeah!

      BUT I can't seem to find it. It doesn't show up in code hinting and 
      putting it in throws a compiler error.

      has anyone had success using(finding) this? (I am using Flex 3 beta 
      2, nightly build 190590) Is this another bug?

      - Kevin







   

Reply via email to