Hi, we are considering using Perlbal as our frontend server to backend Apach
es.

However, would it be more efficient to use Perlbal to serve static
contents(photos and etc) maybe from MogileFS, while passing dynamic
contents to the backend Apaches? This would require a filtering based
on FileTypes requested. Also, if the user wanted to upload new photos,
would it be a problem since the request is dynamic (say PHP) and it
would be passed to the backend servers? Thanks.

-Liang

[ Post a follow-up to this message ]

That's a common setup.  You shouldn't have problems.

- Brad


On Tue, 23 Jan 2007, kingler wrote:

> Hi, we are considering using Perlbal as our frontend server to backend Apa
ches.
>
> However, would it be more efficient to use Perlbal to serve static
> contents(photos and etc) maybe from MogileFS, while passing dynamic
> contents to the backend Apaches? This would require a filtering based
> on FileTypes requested. Also, if the user wanted to upload new photos,
> would it be a problem since the request is dynamic (say PHP) and it
> would be passed to the backend servers? Thanks.
>
> -Liang
>
>

[ Post a follow-up to this message ]

Yeah, i assume this is a common setup. However, I did not find any
information on how to set up the filetype filtering? Can you shed any
light for me on this? Everything I found is using vhost setup, which
means I need to set up an image hostname like img.domain.com as a
vhost in Perlbal.

Another question is that Apache rewrite + proxy can change the URL
like abc.domain1.com to abc.domain2.com internally. Can Perlbal do
this as well? Thanks.

I saw the book contents (book-toc.txt). Sounds like a great book for
newbies like me. Any news on the book?

-Liang

[ Post a follow-up to this message ]

kingler wrote:
> However, would it be more efficient to use Perlbal to serve static
> contents(photos and etc) maybe from MogileFS, while passing dynamic
> contents to the backend Apaches? This would require a filtering based
> on FileTypes requested. Also, if the user wanted to upload new photos,
> would it be a problem since the request is dynamic (say PHP) and it
> would be passed to the backend servers? Thanks.

Note that you'll probably want design your server infrastructure to make
this easier to manage. Eg, put all images to be served by Mogile on
media.domain.com and your normal 'apache' data through domain.com.

Alternatively, I wrote a plugin a while back to support serving files
differently depending on path, so you can serve all files through
/media/ with Mogile, and everything else with Apache.
http://lists.danga.com/pipermail/pe...ber/000261.html

If you want all image files to be served by perlbal without putting them
in a sensible place; there madness lies...

-jeremy

[ Post a follow-up to this message ]