Multi-Tab

[kevin plummer]

When using multi-Tab, should I be able to log into my app as 2 different users on 2 different tabs? When I open the 2nd Tab and point to the web address I am logged in automatically, I guess using the session Q data from Tab 1. Is that right?

[CaseyR]

Hi, Kevin

While Bruce is sleeping,  I am pretty sure that isn't the case.   The access level and logged in status are the same from tab to tab so you can't log in as a second user.   The Mar 20 NetTalk User group spent some time on this issue.

[CaseyR]

I should read better.   Yes, the tabs share the same SessionQueue values which have loggedin,  access level, and a few other entries.   There is also, though, a SessionDataQueue which includes a tab entry used to filter values specific to the Tab that has focus in the browser.   Our GSV and SSV methods use this second SessionDataQueue filtered or primed for the specific tab.

[kevin plummer]

Thanks Casey - That's a shame. I have companies that run multiple DB's and they love to open them in separate Tabs.

[Bruce]

I think it's worth perhaps refining the statements a bit;

a) the Session Data Queue is distinct for each tab. In other words the values in the _session data_ are whatever you set them to be when the person logged in _on that tab_.

b) the "login state" (ie the binary distinction of logged in or not logged in) is shared across tabs. Meaning that if you are in the state of logged in on one tab then you are in the state of logged in on all tabs.

So I think it can do what Kevin wants - but Kevin you need to carefully consider when you are using "must be logged in" as distinct from a specific session value. As long as you are using things in the _session queue_ then you should be able to use distinct databases in different tabs.

cheers
Bruce

[kevin plummer]

thanks Bruce. The current method certainly works well for one of my apps but restricting the "logged in" status to a tab on another would be helpful.