> whats the best way to give one mason application (can be doubled in > directories) to 2 different user groups without handling the user aspect > in the application. > I put my mason app in different apache-htdocs-dirs and built 2 > mason-handler-files (that give different session-ids, I user > apache::session::file for session handling) with 2 apache-configs. > but the problem is, the user gets everytime the session-data from the > app first started. is setting different session-ids for the cookie not > ok?? > In my browser I see the differnt cookies with the differnt ids but my > app-B session has the data of app-A...
Hi Chris Are the cookies given the same name? if so then perhaps only one is sent back by the browser? If so - can you set the cookie yourself: one cookie called AppA and one called AppB ? I may have completely misunderstood you though... with regards Justin ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
