[JSONRPC-37] Add support for both positional and named arguments in RPCs Created: 08/Nov/19  Updated: 12/Jan/21  Resolved: 21/Nov/19

Status: Verified
Project: jsonrpc
Component/s: None
Affects Version/s: None
Fix Version/s: Aluminium GA

Type: Improvement Priority: Medium
Reporter: Richard Kosegi Assignee: Richard Kosegi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

API written by hand like RemoteOmShard and RemoteGovernance is forcing client to use positional arguments invocation style.This become problem once smae API is implemented in other language (or generated from YANG) using named arguments invocation style.

This improvement is about

  • provide API methods in existing interfaces to support both invocation styles
  • add special case handling in proxy code that will delegate invocation of default method to interface itself, rather then do real proxying
Generated at Wed Feb 07 20:05:21 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.