[GH-ISSUE #5113] [Feature Request]

gitea-mirror commented

2026-05-05 14:32:47 -06:00

Owner

Copy link

Originally created by @st249 on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5113

Describe the feature request

Why not use Grpc and Http2 for faster delivery? A grpc tunnel with an agent which connects to the public server, also the ability to add routes of local api to agent database. I had a sample implementation i can contribute on this feature.

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @st249 on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5113 ### Describe the feature request Why not use Grpc and Http2 for faster delivery? A grpc tunnel with an agent which connects to the public server, also the ability to add routes of local api to agent database. I had a sample implementation i can contribute on this feature. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [x] Performance and Scalability - [x] Security - [x] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:32:47 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:32:51 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Jan 7, 2026):

Why not use Grpc and Http2 for faster delivery?

I’m not sure what exactly you mean, or what it has to do with gRPC/HTTP2.

also the ability to add routes of local api to agent database.

The "agent-side routing table / API registry" part is out of scope for frp currently. You can implement it externally instead: keep frp as the tunnel, and run your own gateway/controller to manage routes (optionally generating/updating frpc config and reloading when needed).

@fatedier commented on GitHub (Jan 7, 2026): > Why not use Grpc and Http2 for faster delivery? I’m not sure what exactly you mean, or what it has to do with gRPC/HTTP2. > also the ability to add routes of local api to agent database. The "agent-side routing table / API registry" part is out of scope for frp currently. You can implement it externally instead: keep frp as the tunnel, and run your own gateway/controller to manage routes (optionally generating/updating frpc config and reloading when needed).

gitea-mirror commented

2026-05-05 14:32:51 -06:00

Author

Owner

Copy link

@st249 commented on GitHub (Jan 7, 2026):

I mean why not use of HTTP2 power and GRPC long poling for connecting a local api to a remote service ???

@st249 commented on GitHub (Jan 7, 2026): I mean why not use of HTTP2 power and GRPC long poling for connecting a local api to a remote service ???

gitea-mirror commented

2026-05-05 14:32:52 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Jan 8, 2026):

I’m still not sure what specific information you’re trying to convey. If you mean the communication between frpc and frps, it’s very simple and doesn’t require a more complex design.

@fatedier commented on GitHub (Jan 8, 2026): I’m still not sure what specific information you’re trying to convey. If you mean the communication between **frpc** and **frps**, it’s very simple and doesn’t require a more complex design.

gitea-mirror commented

2026-05-05 14:32:53 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 23, 2026):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jan 23, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:50:37 -06:00

[PR #4006] [MERGED] bump pion/stun to v2 #4887

gitea-mirror referenced this issue

2026-05-05 14:50:54 -06:00

[PR #4056] [MERGED] bump version #4902

No Branch/Tag specified