>
> Just because Python is used doesn't mean that sessions are going to be
> served from memory all the time. If you are using a multiprocess
> configuration for hosting your Python web application, you have to use
> a backend data store of some sort which is visible to all processes.

That depends. First of all, I didn't say it doese cache sessions under 
all circumstances (or other, not user-dependend data that benefits from 
being served from memory). But it *can*, something PHP can't because it 
has no concept of application server side memory. Everything is 
bootstrapped from scratch, everytime.

Regarding the sessions - there is a concept known as session-stickyness
that can be used to have in-memory session while serving the app using
several processes.
It requires usage of a proper load-balancer or such.

This however is probably better suited for no-apache-at-all-scenarios 
because only then you have the needed equivalence of one process to a 
specific IP/Port-binding. At least I'm not aware of apache/mod_wsgi-ways 
to ensure that otherwise.

> A robust Python web application and especially one to be hosted in a
> multiprocess configuration, cant blindly using memory caching
> techniques either. Where it cant use them is where a change through
> one process would invalidate cached data in another process.

Sure, distributed processes have their difficulties. Yet these arise 
unrelated from used language or framework. Whenever you consider using 
caches in multi-process-scenarios (either by keeping objects around in 
memory, or use something like memcached), you have to be careful about 
TTL or think about good invalidation techniques.

Diez

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to