Thanks for those answer.
Still in the idea of developing large scale application: template
might change considering you have acces or group access to one or
another resource. How to protect this resource from other. In other
words:
let's say I have a template 'welcome.kid'
First I'd like login/password part on this template, this is ok. Then
lets supose there is a link to photo that should be accessible only
by 'userA" but not userB, how to ensure that ?
the only way I'm thinking about is something like
<IMG src="/tg_securimg/myimage1"/>
then I must have a python script with argument (image=myimage1) which
check authentification through identity, then check permission and
then send back a png, jpeg or whatever format. Is this possible ? How
would you guys do this ? This is close to building a secure photo
gallery with turbogears ...
thanks
Le 31 oct. 05 à 12:54, Gerhard Häring a écrit :
Benoit Masson wrote:
[...]
- What about load balancing ?
When I was designing a scalable Python web app system recently, it
involved a software load balancer and CherryPy RAM sessions.
You can use Pound as software load balancer (http://www.apsis.ch/
pound/). It allows you to use session detection by Cookie value,
too, among options.
Will we be able to use cluster fot the cherrypy part ?
With Pound and CherryPy RAM sessions, it should work fine.
Separating the database is a basic move, but what about
turbogears sharing sessions between server ?
With the above approach, you explicitly don't share sessions.
Sessions are kept local to CherryPy instances, and the load
balancer makes sure that requests for the same session are always
going to the same CherryPy instance.
or should we look LVS cluster instead so the framework doesn't even
know it is on a cluster ?
I'd try the simpler approach first.
Note that you don't get session failover this way. I decided to
forget about session failover and make the rest of the system easy
to implement and robust. You *do* get normal failover this way. I.
e. if one CherryPy instance dies, Pound will notice and distribute
the load on the remaining instances.
-- Gerhard
