Local Shared Object ("Flash Cookie") path

[WMroczek]

As we all know ;-) SWF-exported application is able to save data on user's computer via INI object (this was discussed HERE). It uses Local Shared Object (A.K.A. Flash Cookie) for storage.

Here's the thing. When creating a flash app in Adobe Flash you can choose where you want the flash cookie to be saved. The two possibilities are:

- the root folder of the domain, example:

C:\Documents and Settings\[user name]\Application data\Macromedia\Flash Player\#SharedObjects\[some string]\[domain name]

- SWF's own, separate folder in the domain's main folder, example:

C:\Documents and Settings\[user name]\Application data\Macromedia\Flash Player\#SharedObjects\[some string]\[domain name]\[SWF path]\[SWF name]

So you have two options to choose from. But MMF SWF builds give you no choice and always use the second option. This way each MMF-produced SWF saves it's flash cookie files to it's own separate folder.

Using the domain's root directory to save flash cookies gives us the option for multiple SWF files to use the same cookie. This creates ability for multiple SWF's form the same domain to communicate with each other via data stored in the cookie. For example - if you have an RPG game and it's sequel in two separate SWFs it would be possible for the second game to load save data form the first one and use a character or part from the first game in the sequel. Or create a cross-game user profile. The possibilities are many.

I assume that there is a specific bit of code in the flash exporter (I'm looking at kcini.dat as the main suspect) that defines the second storage method in the built SWFs. I'd like to know where it is and how to change it to allow MMF-SWF to store flash cookies in the root directory of the domain.

Regards!

[WMroczek]

Even though I lost the contract I this tweak was needed to complete, I still think it would be useful and hope it gets looked into.

Just saying ;-)

[Dynasoft]

It does sound like it could be useful.