-
Notifications
You must be signed in to change notification settings - Fork 590
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
Proposal: Request Reply Resource #7912
Labels
Comments
cc @pierDipi |
Cali0707
changed the title
Proposal: Request Response Proxy
Proposal: Request Reply Resource
Jun 10, 2024
Per discussion in the WG meeting today, I'm moving this to triage accepted |
knative-prow
bot
added
the
triage/accepted
Issues which should be fixed (post-triage)
label
Aug 22, 2024
/assign |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem
While eventing provides components for asynchronous workloads and event processing, it is sometimes useful to make synchronous calls. By providing a Request Response Proxy we can allow users to have this synchronous experience when they want to.
A (very early WIP) feature proposal doc is here: https://docs.google.com/document/d/1vrCfIH9wRrsl8j7XpHK5XiVRgnx5nB4mLHsp0AxU_0Y/edit?usp=sharing
Persona:
Which persona is this feature for?
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve? 10
Additional context (optional)
Add any other context about the feature request here.
A POC of how this proxy could work is here: https://github.com/Cali0707/knative-llm-tool-provider/blob/main/request-proxy/main.go
The text was updated successfully, but these errors were encountered: