On 17 Aug 2008, at 23:52, Stefan de Konink wrote: >> Just to clarify things. The most important point here is that the >> communication between your application logic and the data base is >> performed asynchronously, over a well known and easy to trace >> protocol. >> And of course, being able to use Cherokee's balancing modules >> (policies) >> to split your SQL load among a bunch of servers is also very >> interesting. > > I'm not ignoring this :) But what about authentication? Is only one > view > possible or would it be possible to have multiple sessions for > different > users?
From the Cherokee side, it is just another handler. You can configure it exactly as any other. All the general functionality remains in place: authentication, encoding, access restrictions, etc. Now, from the MySQL side, there will be a single user authenticating against it. I can not really see the case in which it wouldn't be enough though. Think that you can configure as many dbslayer handlers as you wish (with different user, password, data bases and even MySQL hosts) inside the same Cherokee server. -- Greetings, alo. http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
