dashersw/cote

TTL for requests

Open

#148 opened on Jan 20, 2019

View on GitHub
 (8 comments) (1 reaction) (0 assignees)JavaScript (184 forks)github user discovery
help wantednew feature

Repository metrics

Stars
 (2,388 stars)
PR merge metrics
 (PR metrics pending)

Description

I can not find any information for a request TTL option.

As I understand Requester is gathering requests if has no Responder connected (offline for example) These requests have no TTL, and are executed when Responder goes live.

What I want is to set a TTL for the same way as timeout option. So that if my Responder has not gone live in for example 30 secs - just ignore that request.

In my application client based services can do many requests, but if my Responder server will go offline, and then after 10 mins go live - that response is not needed already.

Contributor guide

Research direction
Examine the existing timeout implementation and consider adding a TTL option. Determine how to handle request expiration before a responder becomes available. Update the Requester class to respect TTL and drop stale requests.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65