Skip to content

The purpose of ResourceAPI #35

@CelestialArcadia

Description

@CelestialArcadia

Hello!

I didn't know how else I would reach you, but I have been trying to wrap my head around the "ResourceAPI" purpose,
and it's still not clear to me.

  1. When the angular app trying to communicate with the backend, why not just do so directly with the AuthServer.
  2. And in case I wanted my angular app to communicate with the backend, then the URI should include the "API/controller" in the "ValuesController" class then add - say the "register" URI? it's still confusing, and especially how it ( the resource API ) redirects to "AuthSever".
  3. is it playing like some sort of a gateway? if so, should I configure it if I had to add some logic? - To be more specific in what situation(s) the resourceAPI will serve me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions