-
Notifications
You must be signed in to change notification settings - Fork 511
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
Run flow elements in parallel #164
Comments
Could you explain the use case a little bit more @jmredfern? If you could mark a request as async (e.g. with something |
Closing as there are no plans to implement this for now - can be re-visited and re-opened again later. |
I have a use case for this. We have a route that returns configuration for a home page which in turn gives the client a number of sources to go and get further data from. The second set of requests would be called in parallel by a normal browser. For example the response from the first request could be something like this:
we'd then want to call each source url in parallel. What do you reckon? |
Yeah I see what you're trying to do. That would also require a mechanism to dynamically set up new requests in the running scenario - there isn't a way to do it at the moment. One way to achieve what you're trying to do is a hook function, which can be as simple as |
Ah, yeah, I don't mind hardcoding the response's urls but yeah, that should work for me. I'll report back once I've tried it Thanks |
To simulate browser calls which happen in parallel:
The text was updated successfully, but these errors were encountered: