Skip to content
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

S3s also has an admin-api, websocket rpc, sharing a listener #173

Closed
loverustfs opened this issue Aug 21, 2024 · 1 comment
Closed

S3s also has an admin-api, websocket rpc, sharing a listener #173

loverustfs opened this issue Aug 21, 2024 · 1 comment
Labels
feature New feature or request

Comments

@loverustfs
Copy link

loverustfs commented Aug 21, 2024

Is it possible to add an Admin API to s3s and share the websocket rpc?

There are several benefits:

This makes it easier to read and write objects from other remote nodes, and to implement distributed reading and writing;
s3 service adapter users can freely implement some S3 management functions;

是否可以在s3s 中加上一套 Admin API,并且共用websocket 的rpc?

有以下几个好处:

这样在读写远程其他Node的对象实更方便,更方便的实现分布式读写;
s3 service adapter 用户可以自由实现一些S3的管理功能;

@Nugine Nugine added the feature New feature or request label Aug 21, 2024
@loverustfs loverustfs changed the title s3s一样也写一套admin-api, 再加上websocket的rpc, 共用一个listener S3s also has an admin-api, plus websocket rpc, sharing a listener Aug 21, 2024
@loverustfs loverustfs changed the title S3s also has an admin-api, plus websocket rpc, sharing a listener S3s also has an admin-api, websocket rpc, sharing a listener Aug 21, 2024
@Nugine Nugine added example and removed feature New feature or request labels Aug 25, 2024
@Nugine Nugine added feature New feature or request and removed example labels Oct 26, 2024
@Nugine
Copy link
Owner

Nugine commented Oct 26, 2024

Implemented in #209.

See also

@Nugine Nugine closed this as completed Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants