Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support HTTP long polling #1122

Open
imiric opened this issue Aug 26, 2019 · 1 comment
Open

Support HTTP long polling #1122

imiric opened this issue Aug 26, 2019 · 1 comment
Labels
evaluation needed proposal needs to be validated or tested before fully implementing it in k6 feature new-http issues that would require (or benefit from) a new HTTP API

Comments

@imiric
Copy link
Contributor

imiric commented Aug 26, 2019

A recent support question in Slack brought up testing a SQS endpoint which uses HTTP long polling. k6/http currently only supports synchronous requests, and long polling is a popular feature used by other services as well, so we should look into supporting it.

From a brief discussion with @na--, this will likely require an event loop implementation per VU, which puts us on the road to support promises, async/await, etc., greatly expanding the testing capabilities.

Also see #746 and #779.

@na--
Copy link
Member

na-- commented Aug 26, 2019

I'd say that the event loop issue (#882) is the js-compat issue, this would just build on top of it. Though I'd also add evaluation needed, since we have to decide on the API eventually.

@na-- na-- added evaluation needed proposal needs to be validated or tested before fully implementing it in k6 and removed js-compat labels Aug 26, 2019
@mstoykov mstoykov added the new-http issues that would require (or benefit from) a new HTTP API label Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
evaluation needed proposal needs to be validated or tested before fully implementing it in k6 feature new-http issues that would require (or benefit from) a new HTTP API
Projects
None yet
Development

No branches or pull requests

3 participants