2.2

mos: watson://... RPC call support

URIs should be of the following format:
   watson://org-or-host/devtype/devid
org-or-host is either org id or full messaging host name, i.e. it can be
myorg or myorg.messaging.internetofthings.ibmcloud.com
API key and auth token can be provided as user:password component of
the URI:
   watson://a-myorg-4svdriwzyr:AAA%28-BBBCCDEFFRWD@myorg/mos/esp8266_123456
Note that special symbols in the token, if present, must be URL-encoded.

API key and token can be supplied via command line or environment as well:
`--watson-api-key` / `MOS_WATSON_API_KEY` and `--watson-api-auth-token` / `MOS_WATSON_API_AUTH_TOKEN` respectively.

Includes minor fixes to rpc-mqtt.

CL: mos: watson://... RPC call support

PUBLISHED_FROM=b0a5566b74ba55b83be6a4490b62b93c825c1a97

2.1

rpc-mqtt: Do not double-ACK the message

It's done by the MQTT library.

CL: rpc-mqtt: Do not double-ACK the message (it's done by the MQTT library)

PUBLISHED_FROM=8df95a8b987e22a0b606d3c4b1f8d1a892edc441

2.0

Apache 2.0 for all of apps/libs

CL: Apache 2.0 for all of apps/libs

PUBLISHED_FROM=8d74d4284e3eb8f2651f1e688e6684851a0b3f60

1.26

Implement mg_rpc_get_channel_info()

Also rename `struct mg_rpc_authn` to `struct mg_rpc_authn_info`, for consistency.

PUBLISHED_FROM=41d7eb0a2b56c13dbe947bd92a7e2d0ba4afff50

1.25

Implement mg_rpc_get_channel_info()

Also rename `struct mg_rpc_authn` to `struct mg_rpc_authn_info`, for consistency.

PUBLISHED_FROM=41d7eb0a2b56c13dbe947bd92a7e2d0ba4afff50

1.24

Implement mg_rpc_get_channel_info()

Also rename `struct mg_rpc_authn` to `struct mg_rpc_authn_info`, for consistency.

PUBLISHED_FROM=41d7eb0a2b56c13dbe947bd92a7e2d0ba4afff50

1.23

Implement mg_rpc_get_channel_info()

Also rename `struct mg_rpc_authn` to `struct mg_rpc_authn_info`, for consistency.

PUBLISHED_FROM=41d7eb0a2b56c13dbe947bd92a7e2d0ba4afff50

1.22.1

Implement mg_rpc_get_channel_info()

Also rename `struct mg_rpc_authn` to `struct mg_rpc_authn_info`, for consistency.

PUBLISHED_FROM=41d7eb0a2b56c13dbe947bd92a7e2d0ba4afff50

1.22

Implement mg_rpc_get_channel_info()

Also rename `struct mg_rpc_authn` to `struct mg_rpc_authn_info`, for consistency.

PUBLISHED_FROM=41d7eb0a2b56c13dbe947bd92a7e2d0ba4afff50

1.21

Remove the concept of "trusted" RPC channel

Conceived as a temporary access control measure, this is no longer needed now that we have proper authentication and RPC ACL.

PUBLISHED_FROM=0631244c79c289dbb168ee7537388828a8c55348