Makes sense.  Thanks Zeh.
Maybe you can tell me if there if there is any way to ensure that accessing fla files over the network is stable. I know in the past that flas have disappeared on me when working off a network drive. I'm guessing you'd say that I should duplicate whatever it is and put in on my own local drive and not even risk it, but I thought I'd ask. It's just a mess to have client work all over the place.

If you're only talking about .FLA files, well, yes, it's a mess having them locally. You'd also need to replicate the "deploy" files (ie, html files, images, xmls, other files). Having them over a network is the best choice, although there's the constant problem - since Flash keeps the .FLA file open, if your connection with the server is lost, your .FLA file is doomed and you won't even be able to save it anymore (you'd have to copy everything to a new .FLA file and save it instead). Granted, I haven't had this problem with Flash 8, so I don't know if it's still like this, but it's probably the case.

I'd stick with editing .FLA files over the network, but having a backup policy to backup files at least once a day to a separate place, and remembering to do incremental file naming saves once in a while (ie, index00.fla, then index01.fla, then index02.fla) to avoid a worst case scenario. I've never seen files "disappear" over a network, but the disconnection problem is easy to notice and, most times, easy to fix as long as you noticed it before closing Flash (which is also easy, since you're unable to save).

In the end, the biggest problem you can have a is a power failure -- crashing the server and your computer at the same time would probably be the end for the .fla file.


- Zeh
_______________________________________________
[email protected]
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

Reply via email to