You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Paul Lindner (JIRA)" <ji...@apache.org> on 2008/05/17 16:02:55 UTC
[jira] Created: (SHINDIG-278) For RemoteContentFetcher implement
504 timeouts and Negative Caching
For RemoteContentFetcher implement 504 timeouts and Negative Caching
--------------------------------------------------------------------
Key: SHINDIG-278
URL: https://issues.apache.org/jira/browse/SHINDIG-278
Project: Shindig
Issue Type: Improvement
Components: Gadget Rendering Server (Java)
Reporter: Paul Lindner
Assignee: Paul Lindner
In production we've found it necessary to negative cache failing requests as a self preservation measure.
We also want to return a 504 response if the upstream server times out instead of a generic 500, this helps the developer
understand that the fault lies in the network and not in Shindig.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (SHINDIG-278) For RemoteContentFetcher implement 504 timeouts and Negative Caching
Posted by Kevin Brown <et...@google.com>.
Yeah -- right now I've stuck that on the http response itself, which is a
little hard to work with (and static, not configurable).
Ideally it would be in http fetcher itself, but that would require making
some other changes that I wasn't ready to make myself. If you're feeling
braver than I am go for it :).
On Mon, Jun 9, 2008 at 5:17 PM, Paul Lindner <pl...@hi5.com> wrote:
> I was leaving it open so I could add hooks to customize the negative
> caching ttl
>
> I'll open a new issue for that...
>
>
> On Jun 9, 2008, at 1:05 AM, Kevin Brown (JIRA) wrote:
>
>
>> [
>> https://issues.apache.org/jira/browse/SHINDIG-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Kevin Brown closed SHINDIG-278.
>> -------------------------------
>>
>> Resolution: Fixed
>>
>> This has been in for a while, too.
>>
>> For RemoteContentFetcher implement 504 timeouts and Negative Caching
>>> --------------------------------------------------------------------
>>>
>>> Key: SHINDIG-278
>>> URL: https://issues.apache.org/jira/browse/SHINDIG-278
>>> Project: Shindig
>>> Issue Type: Improvement
>>> Components: Gadget Rendering Server (Java)
>>> Reporter: Paul Lindner
>>> Assignee: Paul Lindner
>>>
>>> In production we've found it necessary to negative cache failing requests
>>> as a self preservation measure.
>>> We also want to return a 504 response if the upstream server times out
>>> instead of a generic 500, this helps the developer
>>> understand that the fault lies in the network and not in Shindig.
>>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
> Paul Lindner
> plindner@hi5.com
>
>
>
>
Re: [jira] Closed: (SHINDIG-278) For RemoteContentFetcher implement 504 timeouts and Negative Caching
Posted by Paul Lindner <pl...@hi5.com>.
I was leaving it open so I could add hooks to customize the negative
caching ttl
I'll open a new issue for that...
On Jun 9, 2008, at 1:05 AM, Kevin Brown (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/SHINDIG-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Kevin Brown closed SHINDIG-278.
> -------------------------------
>
> Resolution: Fixed
>
> This has been in for a while, too.
>
>> For RemoteContentFetcher implement 504 timeouts and Negative Caching
>> --------------------------------------------------------------------
>>
>> Key: SHINDIG-278
>> URL: https://issues.apache.org/jira/browse/SHINDIG-278
>> Project: Shindig
>> Issue Type: Improvement
>> Components: Gadget Rendering Server (Java)
>> Reporter: Paul Lindner
>> Assignee: Paul Lindner
>>
>> In production we've found it necessary to negative cache failing
>> requests as a self preservation measure.
>> We also want to return a 504 response if the upstream server times
>> out instead of a generic 500, this helps the developer
>> understand that the fault lies in the network and not in Shindig.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
Paul Lindner
plindner@hi5.com
[jira] Closed: (SHINDIG-278) For RemoteContentFetcher implement 504
timeouts and Negative Caching
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Brown closed SHINDIG-278.
-------------------------------
Resolution: Fixed
This has been in for a while, too.
> For RemoteContentFetcher implement 504 timeouts and Negative Caching
> --------------------------------------------------------------------
>
> Key: SHINDIG-278
> URL: https://issues.apache.org/jira/browse/SHINDIG-278
> Project: Shindig
> Issue Type: Improvement
> Components: Gadget Rendering Server (Java)
> Reporter: Paul Lindner
> Assignee: Paul Lindner
>
> In production we've found it necessary to negative cache failing requests as a self preservation measure.
> We also want to return a 504 response if the upstream server times out instead of a generic 500, this helps the developer
> understand that the fault lies in the network and not in Shindig.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.