Reputation: 4246
Does a Flex application (by default) enable a user to log in more than once, each time using a new browser window or tab, and not run into any shared memory problems? That is, since it's the same application, the variables cached in local RAM (might) use the same name(?). Does Flex have any issues like this?
Or, since each running application is in a separate browser, they are considered to run independently from each other?
Also, if I add BlazeDS into the mix, does it add any new problems in the above scenario?
Upvotes: 0
Views: 301
Reputation: 13532
They are all running in their own memory space so you won't have any conflicts or anything.
Upvotes: 2