What is the point of having a separate class for detecting the mode (local/remote). Since the calls are made to the PFE api endpoint I would say it should belong to the Server api/client (maybe name this PFEApi). This will keep it consistent with your architecture blueprint.
#3 Updated by ming about 8 years ago
PFE API != Relay API. At least it is not clarified that the PFE server can operate as the Relay server and vice versa. Actually in such case there is no point in establishing connection using
PUT /client, because we would know PFE address for remote access and local address is contained at the
GET /servers result. This is why I see the point in unifying the client and not the API. Or maybe I just don’t understand something.
#5 Updated by cpg about 8 years ago
i did not look at the code, so i cannot make any assertions of what should be done.
but i will clarify that the PFE and the relay are different. they happen to be in the same machine at the moment, but we absolutely 100% do not want to rely on that, or it will be a serious problem if we were to hit some scale/load issues.
Also available in: Atom