-
Notifications
You must be signed in to change notification settings - Fork 28
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
HTTP Cache API: JS SDK #991
Comments
Can we have this by EoY (Q4) as we do have JS customers waiting on HTTP Cache API support ? |
Hostcall parity is exactly the Q4 goal. I haven't fully analyzed the surface area of the new HTTP Cache API yet, and KVStore v2 is next on the list, but it seems fairly likely we should be able to complete this in Q4. |
apologies, but just for my understanding, does "hostcall parity" equate to "JS SDK availability in guest for HTTP Cache API " or something else host specific only? |
Yes we want to fully support the latest host APIs in the JS SDK. |
This is to track the JS SDK additions in Q4 to support HTTP Cache API
The text was updated successfully, but these errors were encountered: