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'm going to use RPC inside golang code without knowledge about method's argument structure at compile time (inside templates). It is based on method name in string and map[string]interface{} for request arguments.
I guess there are 3 ways to get wanted:
reinvent gorilla/rpc's map.go in another package without JSON decoding
fork gorilla/rpc and make public all of service and serviceMethod structs
fork gorilla/rpc and add tiny (33 lines) function with signature like func (s *Server) Call(r *http.Request, decoder func(input interface{}, output interface{}) error, method string, args *map[string]interface{}) (interface{}, error)
What would you advise?
The text was updated successfully, but these errors were encountered:
I'm going to use RPC inside golang code without knowledge about method's argument structure at compile time (inside templates). It is based on method name in string and map[string]interface{} for request arguments.
I guess there are 3 ways to get wanted:
service
andserviceMethod
structsfunc (s *Server) Call(r *http.Request, decoder func(input interface{}, output interface{}) error, method string, args *map[string]interface{}) (interface{}, error)
What would you advise?
The text was updated successfully, but these errors were encountered: