<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi, especially the caching is very important for us, because we want to
keep traffic away from the mp3 repository server.<br>
So you recommend:<br>
Client requests streaming on demand mp3 <br>
- lighthttpd does streaming and requests from<br>
- varnish as reverse proxy/cache from<br>
- mp3 repository<br>
<br>
Best regards<br>
<br>
Andreas<br>
Ole Laursen schrieb:
<blockquote cite="mid:loom.20090212T152954-900@post.gmane.org"
type="cite">
<pre wrap="">Andreas Fassl <a class="moz-txt-link-rfc2396E" href="mailto:afassl@..."><afassl@...></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">after reading the docs it looks like I need an apache server to serve
the cached mp3 content for streaming on demand.
Any experience in configuration of this setup?
</pre>
</blockquote>
<pre wrap=""><!---->
No, but I have set up a site with videos streamed with a Flash widget. We let
the video files pass through the cache unaltered with something like
if (req.url ~ "^/media/content") {
pass;
}
and send the request to a lighttpd backend. Lighttpd is easy to setup to serve
static files, modest in resource usage for this task and scales very well. The
disk cache in the operating system makes sure the files are in memory - it's
just a matter of having enough RAM to keep the requested data in memory. For
this reason, I don't think there's any point in using Varnish's cache in this
kind of setup.
Ole
_______________________________________________
varnish-misc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:varnish-misc@projects.linpro.no">varnish-misc@projects.linpro.no</a>
<a class="moz-txt-link-freetext" href="http://projects.linpro.no/mailman/listinfo/varnish-misc">http://projects.linpro.no/mailman/listinfo/varnish-misc</a>
</pre>
</blockquote>
<br>
</body>
</html>