1 person found this helpful
I am afraid that you cannot delete shared objects created by other swfs. Since security of the data is very important for Flash, the swf file which creates the shared object should delete/clear it. Flash will not allow second swf to clear first swf's data even if they are loaded from same domain or if they are same swf with different names.
If the swf's name is keep changing everytime, it is impossible for the swf with new name to access the shared object of previous swf. In your case, shared object is written but not read until the names match. Not sure why you are generating swf's name dynamically. But it will not work with shared objects.
Thanks for your answer, I suspect as much, just hoping there was something I've missed or a cunning workaround exists. Would be nice if they provided the ability to allow this using crossdomain.xml style config script or somethin. Disable it by default, but for a site which you control, allow local swfs the ability to browse local data for that site.
> Not sure why you are generating swf's name dynamically.
As part of our build process each swf has it's perforce revision postpended to the name, this is to avoid the users getting an old version via his cache and also useful to check versions by looking at traffic or the page source. There are other reasons we might use generated names, obfuscation etc.