Other web frameworks allow you to customise the name of the session cookie to avoid this sort of problem where different applications run on different ports under same host name. Other web frameworks also allow one to cleanly mount multiple instances of an application under different sub URLs of same host/port and where they need different session contexts, allow you to have the session cookie path be the sub URL so they are distinct for each instance.
If web2py can't do this, it is a design/implementation limitation, not a feature. Graham On Oct 21, 12:21 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > It is not going to be the same session. By default each app has its > own sessions and session keys. There is no sharing between apps. You > can, optionally, have one app retrieve the session keys and sessions > of another app but it is not a goo idea. > > Massimo > > On Oct 20, 5:50 am, Alex Fanjul <alex.fan...@gmail.com> wrote: > > > > > Thanks Massimo, > > one quick and maybe newbi question: if you have 2 applications (in the > > same server), and each application has his own session directory to > > store private session data, how does the server know that you are > > openning the "same session" in the two apps? and.. is it actually the > > same session even within the same browser? maybe this concern contexts, > > and so... > > > regards, > > alex f > > > > To clarify. This is not a bug. This is a feature. > > > > As long you store server side, web2py prevents the same user from > > > opening the same session twice. There is no concurrency problems for > > > different users. There is no problem if the same user uses two > > > distinct sessions (by using different browsers or different machines). > > > > Massimo > > > > On Oct 19, 4:44 pm, Alex Fanjul<alex.fan...@gmail.com> wrote: > > > >> Wow, this sounds me!! > > >> In the enterprise I'm working (by now) we have a big social network > > >> product (in a mix of perl and private language), and we in fact suffer > > >> from similar sessions problems/issues. > > >> I deed, if you have 2 applications in the same server the sessions are > > >> messed like this example... > > >> I think this could have to take into consideration. ¿or not? > > > >> Alex F > > > >> El 19/10/2009 16:32, Wes James escribió: > > > >>> On Mon, Oct 19, 2009 at 8:26 AM, SergeyPo<ser...@zarealye.com> wrote: > > > >>>> Run two different web2py applications on same machine using two > > >>>> different ports (127.0.0.1:8000 and 127.0.0.1:8002). Open two browser > > >>>> windows for two apps (two tabs in Safari). > > >>>> Log in 1st application admin in 1st window. > > >>>> Log in 2nd app admin in 2nd window. > > >>>> Try to do smth in 1st window - it will ask you for password. > > > >>>> Is it intended behaviour or sessions do not take port number into > > >>>> account? > > > >>> When you have a browser open, a session is active across all windows. > > >>> The only way to get around this is to open a different browser. i.e. > > >>> browser one is safari, browser two is firefox or opera, etc. Firefox > > >>> 3.5.3 has private browsing, but I don't know how that would work in > > >>> this situation. Does private browsing put your sessions in a black > > >>> box that no other browser window (of the same browser instance) can > > >>> see?? > > > >>> -wes > > > >> -- > > >> Alejandro Fanjul Fdez. > > >> alex.fan...@gmail.comwww.mhproject.org > > > -- > > Alejandro Fanjul Fdez. > > alex.fan...@gmail.comwww.mhproject.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
