At its
most basic, think of a Local Shared Object as a high-capacity cookie.
You're right that it's basically a bunch of name/value pairs, but the "value"
can be just about any object type you'd use. I know even less about your
setup, but since you're talking about getting the information to a server you
probably don't want to replace your mxml survey object, although it's not out of
the question. The advantage of a Local Shared Object survey object over an
mxml survey object is persistence - that is, your data will remain between
sessions, but obviously only locally (on the computer it was created on).
There's no reason you can't have both either - the mxml survey object simply
gets copied to the local shared object and retrieved whenever your app starts
up/user logs in/whatever.
Rick
__._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___ |
- RE: [flexcoders] Re: A web survey based on Flex Rick Englert
- [flexcoders] Re: A web survey based on Flex advantexllc