SharedObject (Flex 3.2) behaving unexpectedly when query string present in URL
- by rhtx
Summary: The behavior detailed below seems to indicate that if your app at www.someplace.com sets/retrieves data via a SharedObject, there is some sort of .sol collision if the user hits your app at someplace.com, and then later at someplace.com?name=value.
Can anyone confirm or refute this?
I'm working on a Flex web app that presents the user…