or for single session only?
Multiple session persistence is what I am looking for.
I don’t understand the question tbh. If you mean more devs in the development environment, then yes. I recommend using MySql/Maria for the project storage instead of SQlite. If you mean running the same application multiple in one browser, then no, the cookies will interfere. The trick is to use different browsers, but there is a maximum 
-or- dive deeply in the code to allow custom session naming. Quite complex. If you mean sticky sessions, then I’m not sure. This depends on load balancers, a rather technical issue, depending on your environment. If you mean to use persistent cookies, I’m unaware of a setting in Scriptcase where you can define that.
1 Like
I meant sticky sessions for use with load balancers
Multiple users logging in to use the componenet, not developers.
Does scriptcase allow for that?
I think so, but am not sure. At the University of Groningen we have over 30000 potential users (students and employees) over our applications, and I know that the University has a complex infrastructure with load balancers, F5, firewalls etc. etc. Our applications runs fine although we have to do some adjustments like proccessing php headers etc. But the applications run fine.
a session is stored per user on the server, but i believe you can choose to store it in a database.
you can force a single session per user , so that they can login only on one device at a time.
multiple sessions might interfere but it will work.
the problem i had with sessions is that they expire after 10 minutes or something of inactive use . it changed all possible php /server variables , no matter what, the session expires earlier than I want.
I am referring to storing session data in a database table, so that if a Load Balancer has to kick in, the sessions can be static and not lost.