-
1. Re: Quick shared object question.
Ned Murphy Jul 15, 2011 10:32 AM (in response to cane2980)Think of a shared object like a cookie... it is something that is stored on the user's machine. So you cannot have other users make use of someone else's 'cookie'.
You would likely need a database if you intend to have information about multiple users being visible to all currently accessing the application.
-
2. Re: Quick shared object question.
cane2980 Jul 15, 2011 5:10 PM (in response to Ned Murphy)Ok Ned, thanks by the way, that kind of helps. In the example I saw on the of the timed viewing on the web page, when the shared object was activated, it downloaded to my hard disk like a cookie, that makes sence.
But I've also read about a shared object being used to parse messages in a chatroom. So, if I'm now understanding how it works correctly... Then in like a chatroom environment, my swf places a call to the server as "get remote sharedObject", the shared object downloads to my swf and waits there, when another user types a message it goes to the shared object. My shared object, because it's shared, grabbs the message and parses it in my text window. Of course you have to program around stack message issues when more than one person sends a message at the same time.
Am I now getting the hang of how it works correctly?
thanks again;
-
3. Re: Quick shared object question.
dmeN Jul 16, 2011 8:59 AM (in response to cane2980)Like Ned said, the SO is local to each machine... remember Flash plays at the client - so regardless of how many people are playing the game the data in the SO is unique to them. You only ever need the one object...
-
4. Re: Quick shared object question.
cane2980 Jul 16, 2011 11:38 AM (in response to dmeN)yes, thank you very much. This clears up a lot of thing for me. In one of my books it says when you use the flush comand it dumps the information the hard disk on the server. That appears to be incorrect. What it should say is it dumps it to the hard disk of the flash player using the shared object. Wow a typo in an actionscript 3 book... Go figure!




