An implementation-specific feature is a Gateway API feature whose behavior and semantics depend on the particular implementation providing it. Unlike portable features, it cannot be transferred to another implementation without changing configuration. section 13.1.2
Gateway API features differ in how safely they transfer between implementations:
- Core features are standard, portable, and required for every Gateway API implementation. section 13.1.2
- Extended features are portable when supported, but individual implementations may omit them. section 13.1.2
- Implementation-specific features are not portable because their behavior and semantics depend on the implementation. section 13.1.2
Changing implementations
A configuration using an implementation-specific feature cannot move directly to a different Gateway API provider. Switching providers requires configuration changes because the feature’s behavior and semantics may differ. section 13.1.2
