ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-388) Add support to send "back-off time" headers.
Date Tue, 01 Oct 2013 11:28:24 GMT


Marcel Offermans commented on ACE-388:

On 1) I agree that it would be nice if we can come up with an implementation that allows us
to easily apply back-off headers to other requests. At least to all interactions with the
management agents. If we want this for our client APIs as well is debatable to me as clients
can be deployed anywhere and work completely separate from the server, so I don't anticipate
that we want to use back-off there initially.

On 2) we must have some kind of configurable strategy here. The two examples Bram mentions
(# of concurrent downloads and lazy store calculation) are two good examples of what needs
to be supported. Some kind of whiteboard style interface that can decide to send a delay makes
sense. That way we could even have multiple (in which case we should probably either ask all
of them and choose the highest back-off time, if any, or simply stop when we found the first
back-off time, in which case we might want to sort the implementations by service ranking
as well...).

> Add support to send "back-off time" headers.
> --------------------------------------------
>                 Key: ACE-388
>                 URL:
>             Project: ACE
>          Issue Type: Task
>          Components: Deployment
>            Reporter: Marcel Offermans
>            Assignee: Angelo van der Sijpt
> Add support to send “back-off time” headers if the server is too busy. Make the “come
back later” time configurable.

This message was sent by Atlassian JIRA

View raw message