Ole Laursen writes:
> Andreas Fassl writes:
> > Hi, especially the caching is very important for us, because we want to
> > keep traffic away from the mp3 repository server.
> > So you recommend:
> > Client requests streaming on demand mp3
> > - lighthttpd does streaming and requests from
> > -
rling Smørgrav
Gesendet: Fre, 13.2.2009 14:00
An: Poul-Henning Kamp
Cc: Ole Laursen ; varnish-misc@projects.linpro.no
Betreff: Re: Varnish and mp3 streaming on demand
"Poul-Henning Kamp" writes:
> No, we never stream pass, the current design is aimed at freeing
> up the backend as fas
"Poul-Henning Kamp" writes:
> No, we never stream pass, the current design is aimed at freeing
> up the backend as fast as possible, and we only start to transmit
> the object to the client once we have all of it.
Perhaps it is time to consider adding a third option: "stream", which
streams the c
Poul-Henning Kamp writes:
> >Right now pass in vcl_recv is streaming, right?
> >You're only talking about if the
> >object is entered into the cache? Or both cases?
>
> No, we never stream pass, the current design is aimed at freeing
> up the backend as fast as possible, and we only start to tra
In message , Ole Laursen writes:
>Poul-Henning Kamp writes:
>
>> This is necessary to be able to decide, per object, if it should be
>> stored in temporary (malloc) or persistent (disk) storage.
>>
>> With some extra work, this will allow pass to become streaming.
>
>Right now pass in vcl_recv is
Poul-Henning Kamp writes:
> This is necessary to be able to decide, per object, if it should be
> stored in temporary (malloc) or persistent (disk) storage.
>
> With some extra work, this will allow pass to become streaming.
Right now pass in vcl_recv is streaming, right? You're only talking ab
Andreas Fassl writes:
> Hi, especially the caching is very important for us, because we want to
> keep traffic away from the mp3 repository server.
> So you recommend:
> Client requests streaming on demand mp3
> - lighthttpd does streaming and requests from
> - varnish as reverse proxy/cache from
In message <49945b51.90...@progis.de>, Andreas Fassl writes:
>Hi, especially the caching is very important for us, because we want to
>keep traffic away from the mp3 repository server.
>So you recommend:
>Client requests streaming on demand mp3
>- lighthttpd does streaming and requests from
>- va
Hi, especially the caching is very important for us, because we want to
keep traffic away from the mp3 repository server.
So you recommend:
Client requests streaming on demand mp3
- lighthttpd does streaming and requests from
- varnish as reverse proxy/cache from
- mp3 repository
Best regards
A
Ole Laursen writes:
> 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.
In other words, unless you need some other feature of Varnish, you might as well
route the requests
Andreas Fassl writes:
> 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?
No, but I have set up a site with videos streamed with a Flash widget. We let
the video files pass thr
Hi,
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?
Any pointer/hint is greatly appreciated.
Best Regards
Andreas
___
varnish-misc m
12 matches
Mail list logo
