You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, @phal0r !
I've been wandering around seaweedfs since we need some sort of DFS for middle-end architecture. Seaweed is well suited for us, mainly because it provides a set of filer API(To be specific, we'll store wepack's output files to seaweedfs, so directories and file names are particularly important for us).
So I'd like to know if filer API will be added in the future.
The text was updated successfully, but these errors were encountered:
Hi @aliwalker ,
I did not work with filer yet, so I have no experience using it. What I read from the docs, I think integration should be quite straight forward.
Accept a config param for a filer instance (maybe using namespaces to support different filers)
Enhance the API to route filer requests to the filer server
So it is not much to do client-side. Do you have other use cases that are not covered with this approach?
Yes, the filer API is really straight forward to add. I've copied your code directly and modified a bit. See this. It is a framework specific plugin and I added your copy right notice in the source code there.
Since I'm not an experienced engineer yet, my opinions might be immature 😁:
Due to simplicity I just decided one filer per server is fine for our needs, and added explicit xxxFiler() methods to distinguish them.
I think the original APIs are just fine. No need to changes their functionalities.
Still, I think that Filer APIs could be an enhancement to this library.
Hi, @phal0r !
I've been wandering around seaweedfs since we need some sort of DFS for middle-end architecture. Seaweed is well suited for us, mainly because it provides a set of filer API(To be specific, we'll store wepack's output files to seaweedfs, so directories and file names are particularly important for us).
So I'd like to know if filer API will be added in the future.
The text was updated successfully, but these errors were encountered: