Hosting different FASP API endpoints on different domains

[oneiros]

To scale a resource-heavy FASP it might be beneficial to split it into different components that are hosted on different (sub-)domains.

The current specification relies on a FASP having one canonical base URL that includes a domain which cannot be changed.

Maybe a FASP could specify a domain or base URL per capability (maybe in its provider_info endpoint?).

I would like to postpone this decision a bit. Luckily, the first "real" provider we need to implement is a search and discovery provider. This is a resource-heavy tasks and I hope we will learn more about its actual requirements from that experience.

See here for a discussion: #36 (comment)