We are running into a baffelling behavior using SharedObject.
We have a a few Desktop Flash applications: One is a main application, the
other an update utility for the main app. They use a Flash Cookie to find each
other, as the main app could be installed anywhere (USB, C). The apps are
based in Director using the Flash8 Xtra.
Say we start with a completely empty SharedObjects folder
Running the main app sets a cookie into a folder like
....Flash Player\#SharedObjects\BFYLPV7P\localhost\02000.sol
via a call like
var so : SharedObject = SharedObject.getLocal ("02000", "/");
where "/" should see the root of the Flash Cookies.
then say Pandora (or any other flash based website using cookies) runs it
generates a new sandbox
....Flash Player\#SharedObjects\2S7GJDMQ\pandora.com
and then all future read requests are against that new '2S7GJDMQ' folder
instead of the "BFYLPV7P" folder, and then neither the app or the updater, can
see the old shared local object folder anymore. Which in the case of it
containing lots of persistent configuration data, is the equivalent of clearing
the Browser cache and forgetting everything.
Trying to understand how it's created, I can delete the contents of the shared
Objects folder and then republish in the Flash IDE and get a new hash for the
folder every time so it seems to be either random or time based. It's not as
far as I can tell the behaviour documented, it's certainly not behaving as I
would expect.
Anybody have any ideas?
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
