Hi Thierry,

For my registered users, I use a unique identifier corresponding to their contact details. But some open multiple tabs.
What do you advise me to add to this 10 character identifier ? INT (SECONDS()) for example ?

Hi Vincent,

do you mean your users work in several browser tabs? If so the browser send the same cookies regardless of the tab, so there's no way to prevent that.

can you describe situations where it's harmful?

If so the browser send the same cookies regardless of the tab, so there's no way to prevent that

But in my form, with partners, I have wUserLogIn(Partners.Id_Partner)

Please describe the undesired behavior more precisely, I just can’t figure what happens.

In fact, I have 2 problems which I try to eliminate the possible sources:

1 - A click on the link of a folder (Accesdos IN xxxserver) causes a disconnection on the 1st attempt, OK on the second

2 - Sometimes, my main table is locked (although of course I don't have an exclusive opening).

Hence my research on login ID

Thanks in advance for any track

Changing wUserID will not help

1. Is very specific to your app. and requires some debugging

2. Is due to a lock not released before the end of the user event that sets the lock. Not a matter of a table being used exclusive

Hi Thierry,

If I open the same screen from 2 different tabs of the same browser, the data of the 1st folder are displayed in the 2d.
The same experience with 2 different browsers does not cause data mixing.
Is there a solution that a user can open two different folders from 2 tabs of his browser ?

Hi Vincent,

as I explained earlier, standard FoxinCloud offers no support for this scenario.

This is a real demand from users

Is an evolution possible ?

Is an evolution possible ?

Complex question…

FoxinCloud Web Application Server (FWAS) identifies a user (browser) using a random cookie (named using the app. code 'xxx') and, if user has disabled cookies, a query string parameter named userID passed along with AJAX requests after form initialization (https://xxx.fr/MethExec.doo?&MethAddr=InitControlsInet&ObjAddr=form_scx&UserID=&PageInit=true&nReq=1).

FWAS uses this userID as session ID, and stores whatever user ID for the application (wUserLogIn(appUserID)) in the session.

Your app. uses 2 cookies: standard FoxInCloud ('doo') and custom ('refdossier'):

The browser sends the same cookies for all tabs opened on the same URL. No differentiation is possible.

Using session Storage, we could maybe generate a tab ID, store it into sessionStorage and append it to &UserID=, and open a new session if the server sees this tab ID appended…
Would require a in-depth analysis to avoid any side-effect.

Thank you for this very comprehensive analysis

I also saw the reference to BroadcastChannel, but this new interface does not work with Safari.

People really all get into the habit of opening multiple tabs, and I can't prevent them either.