FlashMX 2004 cache problem
- Author: Ben
- Filed under: RIA
Apr 4,2004
While developing my first RIA, i ran into a freaky problem when using external class files which are located on a network drive, instead on my local drive.
It seemed flash caches the class files when compiling, and checks the timestamp of every class on compiling to see if it should get the latest version. When using a networked drive, these timestamps seem to get mixed up and scr%wed.
Macromedia identified this problem, but didn’t give a good solution for it. The only fix seems to be to store your class files locally :( (how lame can it get…)
So if you are editting classes and don’t see the desired results when testing your flash movies, think about this, it might be a cache problem. (WOohoo, back to our great dhtml days ;) )
Categories
Archives
- December 2008
- October 2008
- September 2008
- February 2008
- October 2007
- September 2007
- August 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- March 2006
- November 2005
- October 2005
- August 2005
- July 2005
- May 2005
- April 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
Links
Meta
Recent Comments
- Callum on Multi-touch interaction with flash
- Ben on Multi-touch interaction with flash
- Ben on Multi-touch interaction with flash
- Ben on Multi-touch interaction with flash
- desopolis on Multi-touch interaction with flash
View Ben Smeets's profile
One Response for "FlashMX 2004 cache problem"
While working over more than 12 packages and more than 250 action script files, I came across the same problem under Flash 8. Mike Chambers utility for deletion of ASO files, didn’t seem to be that powerful.
However, there is a comment on the technical note by Adobe.
While working with VSS, I first, gathered the “Latest Version” from VSS. For experiment, the Date on VSS was 2007.
Then, I “checked out” an Action Script file from a remote file system (VSS with the option unchecked, “Don’t get local copy”), and then updated it. The Date-Time for that file was 2007 ahead of “checking out” while my local system was running on 2005.
Then I updated the AS file and saved it, a copy of it was saved locally (thus giving the local timestamp of 2005). Later, the file was “Checked In” to the VSS, as you can vision, the timestamp reflected on the server was the result of my local save. That is 2005.
This means if you are working with VSS on the network and you have the option checked “Don’t get local copy”, while “checking out” any file, you are in a big trouble if your system is running with a time lower than that of VSS.
Leave a reply
You must be logged in to post a comment.