...
/products/out-special?$type=OwnProductContent.
Efficiency Considerations
When you set up a routing configuration like this, there is a potential significant efficiency penalty, because it requires Lynicon to send a request to the Data API for each of the potential types which may exist on the matched url. This can be mitigated in the case where there is caching of summaries by setting the static TypeCheckExistenceBySummary property on DataRoute type. This is a Func<Type, bool> which tells the DataRoute infrastructure whether it should check for the existence of a given type by requesting its summary rather than the full record.