Sven Krieger

I would suggest we add features only into the documentation if they are already working. It's mentioned here: http://v3-apidocs.cloudfoundry.org/version/3.122.0/index.html#share-a-route-with-other-spaces-experimental

For me a feature which is described in the documentation, even it is marked as experimental, should be something like a MVP. So it should bring some kind of value...

Mapping shared routes to apps should work now, as the PR was merged. Closing this issue.

One topic to discuss is how to handle large result sets of included resources. E.g if the app has 1000 routes. An idea would be to set a limit for...

@sethboyles - On our biggest landscapes we can see apps with 300+ routes. This is due to multitenancy. - As the [hard limit for routes per app](https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html#routes:~:text=The%20number%20of%20routes%20that%20can%20be%20mapped%20to%20each%20app%20is%20approximately%201000%20(128%C2%A0KB).) seems to be...

We tried to come up with a concept which would work for show and list endpoints as well. We liked the idea to use the already present pagination for included...

I like the idea of having the platform deal with it instead of the users. This idea is worth to be analysed further. Just one thing which might cause problems...