thanks Jens K. and Hemant K.!!!
more questions and clarifications if i may…
apache mod proxy balancer buffers requests to pass to the rails app or
does the proxy pass requests to each mongrel instance? im thinking
basically when running mongrels, i should be thinking of instances of a
rails app where there is no root rails app right?
memcache, the cache is loaded in memory, outside the rails app, and not
duplicated by mongrel instances. each mongrel instance can read from
can workers of the middleman exist on a different physical machine? so
if the middleman is on his own handler, he can pass off jobs to workers
to determine how many workers i can have on a box, i would have to
determine how much load i would like the workers to handle, and how cpu
intensive is the particular job for the worker?
the middleman buffers jobs in a queue to pass to the next available
big question about video site!
a form with a few text fields and a file field for video. when this form
is submitted, it would be submitted to my rails app and data would be
saved(title, author, text, video etc…). i then would like to pass the
video file off to the middleman so he can scedule a worker to
convert/store the video. now this video, as it is being transferred from
the client to rails app, is it being uploaded to a rails app directory
(hence tieing up a mongrel process), or can mongrel pass that incoming
file quickly to the middleman and then the incoming download is now
outside the mongrel process so the middleman can start work? ive read
the mongrel tutorial and i know the conversion can be outside mongrel,
but i am not too sure about the actual client upload to server
process…wouldnt that tie up a mongrel?