On May 21, 12:49 pm, "Mike Orr" <[EMAIL PROTECTED]> wrote:
> He did say scalable and video, which I took to mean ultra-heavy use of
> very large files, and overkill didn't matter. The disk space alone is
> one reason why static content might want to be on a separate box, so
> it can be plugged into a large disk array or replicated easier, etc.

Ah yes ( that was my , btw ).  At first its not going to be much
content in quantity - just a few large files.  A sep box might be a
good idea.  Thanks for looking out to me!

> By handle you mean a database connection?
Yep.  Read/Write/Log/Session
I'm still trying to figure out a way to consolidate them all into
'cloned' handles under pylons - for small apps hitting 1 db its a bit
of overkill.  The last few times I had to cluster an app and built
with this forethought though, all I had to do was create

> So how do you handle writes?  You direct them all to one master server
> and let it propagate the changes to the slaves? Have you found a good
> replicable database among the free ones that work with SQLAlchemy?
Postgres (through extensions)- though I haven't used replication under
SQLAlchemy or Pylons yet.  I don't assume there will be any problems.

This doesn't solve the need to partition - but let's be honest... if
you're successful you need to Cluster/Replicate; if you SUCESSFUL!!!
you need to partition - and by that time you have the resources to
have a team of engineers handle that exclusively.

> What do you mean by authticket?

http://www.openfusion.com.au/labs/mod_auth_tkt/

it's a great plugin for apache; perl support is official, there are py
php and other contribs.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to