One company mentioned their perl based large scale sns site at YAPC::Asia
IIRC - sorry it might have been six apart as mentioned above, can't remember
which. I do know they wrote their own system to be able to basically split
and merge their user pool according to user name (alphabetical order)
At 21:58 2007-10-26, Mesdaq, Ali wrote:
I personally think that storing images in the DB is the best place to
start because if other better solutions are available later you can very
easily migrate. But if you start out with filesystem migration is a
little bit more cludgy in my opinion. I mean
wrote:
At 21:58 2007-10-26, Mesdaq, Ali wrote:
I personally think that storing images in the DB is the best place to
start because if other better solutions are available later you can very
easily migrate. But if you start out with filesystem migration is a
little bit more cludgy in my
On 10/26/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
NFS gets a bad wrap, as long as you do sane planning and lay it out
properly NFS works very very well for servicing static files to the
webservers. Breaking out to S3 seems silly (Amazon is out to make money
with S3 and if you do it
--
-Original Message-
From: J. Shirley [mailto:[EMAIL PROTECTED]
Sent: Friday, October 26, 2007 12:31 PM
To: The elegant MVC web framework
Subject: Re: [Catalyst] Hypothetical Site and Scalability Planning
On 10/26/07, Mesdaq, Ali [EMAIL PROTECTED] wrote
