Nodejs 在内部调用另一个端点，无需 Axios 并访问该端点的中间件
我有一个场景，我必须注册一家企业并为该企业的每位董事创建帐户。因此，我应该在 /business post 请求成功后点击 /auth/user API 并将响应发送给用户，而无需等待用户帐户创建响应。我在 /auth/user api 的中间件中编写了一些用于护照的功能，因此我无法将其作为单独的函数并在内部调用它来实现此目的。我可以通过使用 Axios 调用 API 端点来实现这一点，但我想知道是否有更好的方法来实现这一点。感谢这里的任何帮助。
I have a scenario where I will have to register a business and create account for each directors of the business. So I should hit /auth/user API after /business post request is successful and send out the response to the user without waiting for the user account creation response. I have some features written in the middleware of /auth/user api for passport so I cannot make it as a separate function and call it internally to achieve this. I can achieve this by calling API endpoint using Axios, but I want to know if there is any better approach to achieve this. Appreciate any help here.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为，在API程序中，组件应该以特定的方式分离，访问控制应该由中间件和装饰器来处理。我主要使用这种方式，例如通过创建一个中间件来验证用户登录。在其中，我执行身份验证操作，当出现错误时，我会创建一个错误。但是，例如，如果它通过了该阶段，我会在请求中设置会话值并允许其进入下一个阶段。这样，当它到达我的处理程序时，身份验证已执行并且会话值已返回。在某些场景中使用装饰器也很有用。这种方法允许我在任何地方使用该中间件。
我不确定我对你的意思的理解程度如何，但无论如何我希望这会有所帮助。
In my opinion, in an API program, components should be separated in a specific way and access control should be handled by middleware and decorators. I mainly use this approach, for example, by creating a middleware to verify user login. Inside it, I perform authentication operations and when an error is reached, I create an error. However, if it passes that stage, for instance, I set the session values inside the request and allow it to move to the next stage. This way, when it reaches my handler, both authentication has been performed and session values have been returned. Using decorators can also be useful in some scenarios. This approach allows me to use that middleware anywhere.
I'm not sure how well I understood what you meant, but I hope this helps anyway.