Hi, Thanks for the information. I will start working on it, please feel free to join me.
Best regards, Jinsong On Wed, Jul 10, 2024 at 11:17 AM ConradJam <czy...@apache.org> wrote: > Thanks for starting this discussion. > > +1 > > Qishang Zhong <zhongqish...@gmail.com> 于2024年7月10日周三 10:17写道： > > > Thanks for starting this discussion. > > > > +1, Unity the APIs for easy understanding and maintenance. > > > > Best, > > Qishang Zhong > > > > Congxian Qiu <qcx978132...@gmail.com> 于2024年7月9日周二 14:51写道： > > > > > Thanks for driving this, +1 to unify the API. > > > > > > I was confused by two sets of also when reading the code recently. As > > far > > > as I can see, the unified set of APIs can support the fronted and Open > > API > > > calls -- they are both the client of the Rest API, maybe we'll need to > > > support different auth validation methods for different scenarios, but > > this > > > is not a huge issue. > > > > > > Best, > > > Congxian > > > > > > > > > Jinsong Zhou <jinsongz...@apache.org> 于2024年7月9日周二 14:32写道： > > > > > > > Hi devs, > > > > > > > > Currently, AMS provides two sets of HTTP APIs. One set is used by the > > > > frontend component Dashboard, while the other set serves as the Open > > API > > > > for other ecosystem dependencies. These two sets of APIs have > different > > > > prefixes, but many of their definitions and backend implementations > are > > > > actually the same. > > > > > > > > Maintaining two sets of APIs will require additional maintenance > work. > > > > Therefore, I am wondering if we can unify and use a single set of > APIs > > > that > > > > can meet the requirements of both the Dashboard and the ecosystem. > > > > > > > > I am open to hearing your thoughts. > > > > > > > > Best, > > > > Jinsong > > > > > > > > > > > > > -- > > Best Regards, > > Qishang Zhong > > > > > -- > Best > > ConradJam >
