On 6/12/12 5:43 PM, Nick Kew wrote:
On Tue, 12 Jun 2012 16:51:42 -0600
Yeah, I totally agree. There are some potential alternatives here, such as
fixed sized chunking of content perhaps. It's still a difficult problem to
solve optimally for every type of request. Your suggested heuristics
probab
On Tue, 12 Jun 2012 16:51:42 -0600
Leif Hedstrom wrote:
> On 6/11/12 11:20 PM, Nick Kew wrote:
> > On 12 Jun 2012, at 02:49, Leif Hedstrom wrote:
> >
> >> Another option that I've been pondering, which is more suitable for large
> >> contents I think, is to kick off background requests for the fu
On 6/11/12 11:20 PM, Nick Kew wrote:
On 12 Jun 2012, at 02:49, Leif Hedstrom wrote:
Another option that I've been pondering, which is more suitable for large
contents I think, is to kick off background requests for the full objects. A
plugin that does something like:
Thoughts?
I seem to recol
Yes. For a range request, if it cannot be satisfied by cache, is just passed on
to the origin server. This is because there is no good thing to do with the
request as partial responses cannot be cached and (as noted) always fetching
the source object is not a good thing.
This hasn't come up muc
On 12 Jun 2012, at 02:49, Leif Hedstrom wrote:
> Another option that I've been pondering, which is more suitable for large
> contents I think, is to kick off background requests for the full objects. A
> plugin that does something like:
>
> Thoughts?
I seem to recollect discussing approaches to
>
> 1) In read-response-header hook, if the object is a Range response, *and*
> it's cacheable, schedule a background load on the task threads. This
> obviously has to be done in a way that the same request is only fetched
> one,
> effectively "locking" it.
How do i schedule a background load on
On 6/11/12 5:34 PM, James Peach wrote:
> On 11/06/2012, at 4:23 PM, 오재경 wrote:
>
>> Hi.
>>
>> we have an serious issue. we have a customer site whose service is online
>> learning and it provides registered members with a player. the player sends
>> range request.
>>
>> Now you can guess what prob
> On 11/06/2012, at 4:23 PM, 오재경 wrote:
>
>> Hi.
>>
>> we have an serious issue. we have a customer site whose service is online
>> learning and it provides registered members with a player. the player sends
>> range request.
>>
>> Now you can guess what problem I confront. we have to cache c
On 11/06/2012, at 4:23 PM, 오재경 wrote:
> Hi.
>
> we have an serious issue. we have a customer site whose service is online
> learning and it provides registered members with a player. the player sends
> range request.
>
> Now you can guess what problem I confront. we have to cache contents but
>
Hi.
we have an serious issue. we have a customer site whose service is online
learning and it provides registered members with a player. the player sends
range request.
Now you can guess what problem I confront. we have to cache contents but
because of the range request traffic server can’t cach
10 matches
Mail list logo