You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have writen some service using the code generated by apache official tool,then use go-thrift in the client,but the client failed to call the service.Is it compatible with codes generated by the official tool ?
The text was updated successfully, but these errors were encountered:
The serialization and RPC protocol are fully compatible, but the generated code and package interface are not. I took a different road with this package trying to make it smaller and nicer to use by being more natural Go. This package includes a generator though that you can use to create compatible structs and RPC interfaces if you like.
If you're having difficulties with communications between client and server the cause I've most often seen is difference in either using a framing or non-framing transport.
Thank you.I have used the non-framing transport and the commutation is ok .
But in the my project.The number of one struct fields is 103 , larger than 64.So I think using a bitset struct in structMeta other than uint64 may be better.
I have writen some service using the code generated by apache official tool,then use go-thrift in the client,but the client failed to call the service.Is it compatible with codes generated by the official tool ?
The text was updated successfully, but these errors were encountered: