Implement Vulcain directly in API Platform Core
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- php
调研方向
首先检查 API Platform providers 和现有的 "property" 过滤器，因为 issue 将它们确定为相关的切入点。完成的标准是将 Vulcain-style early hints 和过滤功能直接实现到 API Platform Core 中，但 issue 没有指定具体的文件或测试。
由索引模型根据 Issue 内容生成。
描述
The API Platform distribution has been including the Vulcain Gateway server for some time now.
Since API Platform 3.2, the API Platform distribution also uses FrankenPHP, which allows the HTTP status code "103 Early Hints" to be used directly from PHP.
Although the Vulcain Gateway server now supports the sending of 103 Early Hints in addition to HTTP/2 Server Push, this is almost useless do that in the gateway server: the Gateway server must retrieve the full JSON response from the upstream PHP server before it can calculate which resources to send. If the response is already in the cache of a reverse proxy, sending 103 is useless (the final response containing Preload hints added by the gateway server will be sent immediately). Otherwise, the proxy will have to wait for the JSON to be generated by the PHP server before calculating the 103 links, so we're in the same situation.
What would be better - in case the response is not already in the reverse proxy cache - would be for the PHP server to send the 103 response as soon as possible: ideally, in Platform API providers, when the data has been retrieved from the persistence layer, but before serialization generation (which is known to be a tedious task).
In addition to preloading, it would be interesting to also implement the filtering part of Vulcain (building on the existing "property" filter). This would not be very useful for responses that can be cached (it's better to store the complete response in the cache, and let the proxy do the filtering), but it will prevent some useless work when the response isn't cacheable.
- 主要语言
- PHP
- 星标
- 2.6k
- 派生
- 989
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 102
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
api-platform/core 的其他 Issue
-
JSON:API: resource schemas (`*.jsonapi`) have `properties` but no `type: object`可能已有人在做 @ousamabenyounes 于 1 天前认领。 未关闭
难度 2/5 1 小时以内 新手友好度 80/100
api-platform/core#8701 ·
维护者通常 1 天内回复
-
JSON:API: `JsonApiCollectionBaseSchemaNoPagination` declares `data` as `type: array` without `items`未关闭
难度 2/5 1-3 小时 新手友好度 82/100
api-platform/core#8699 ·
维护者通常 1 天内回复
-
api:openapi:export --spec-version=3.0.0 outputs `webhooks`, which is invalid in OpenAPI 3.0可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
api-platform/core#8690 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
api-platform/core#8680 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
api-platform/core#8725 ·
维护者通常 1 天内回复
查看 api-platform/core 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 88/100
-
难度 2/5 1-3 小时 新手友好度 88/100
grokability/snipe-it#19857 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 92/100
维护者通常 1 天内回复
-
Authentication / Authorization Feature: Volunteer
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
WordPress/mcp-adapter#399 ·
维护者通常 1 天内回复