Macromedia Flash Server - Architecture issue - persisting of data in .fso files

This is Interesting: Free IT Magazines  
Home > Archive > Macromedia Flash Server > May 2006 > Architecture issue - persisting of data in .fso files





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Architecture issue - persisting of data in .fso files
Angel

2006-05-18, 1:11 pm

Hi there

We're building an enterprise-level system and are curious to know how =
others are persisting the data to a database in the shared object files. =
At the moment we're assuming we'll just store the references to the =
right shared object in the database rather than the data itself. This =
isn't a big deal but we are a bit worried about having the data just =
sitting around in a million .fso files for weeks at a time (as users =
need to keep going back to them in our app). It seems most FMS systems =
don't seem to have to worry so much about persistence.

Anyone got any references on how best to do this?

Thanks!

Angel
________________________________________
_______
FlashComm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com