New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support of polymorphic types #638
Comments
IMHO we should delete this header ( |
Could it allow a user to add custom codecs (which would take precedence over the default codec) for some complex cases? |
I learned that we can only have one argument in the service interfaces. What if we wrap all interface arguments in an array and pass an array of types or other information to decode? |
@eutkin |
It's agreed it can be solved on encoder/decoder level. Closing. |
Subj.
Consider to write header
_type
conditionally to the response message. For example it's possible to deduct that class in return type (or in@Response
annotation) is abstract or interface and store this polymorphic indicator (e.g.boolean morph
flag) in theMethodInfo
.The text was updated successfully, but these errors were encountered: