TimeZone API
Version: 1.0.0
Status:
TimeZone interface for Thunder framework.
(Defined with ITimeZone in ITimeZone.h)
Table of Contents
Introduction
Scope
This document describes purpose and functionality of the TimeZone interface (version 1.0.0). It includes detailed specification about its properties provided and notifications sent.
Case Sensitivity
All identifiers of the interfaces described in this document are case-sensitive. Thus, unless stated otherwise, all keywords, entities, properties, relations and actions should be treated as such.
Acronyms, Abbreviations and Terms
The table below provides and overview of acronyms used in this document and their definitions.
Acronym | Description |
---|---|
API | Application Programming Interface |
HTTP | Hypertext Transfer Protocol |
JSON | JavaScript Object Notation; a data interchange format |
JSON-RPC | A remote procedure call protocol encoded in JSON |
The table below provides and overview of terms and abbreviations used in this document and their definitions.
Term | Description |
---|---|
callsign | The name given to an instance of a plugin. One plugin can be instantiated multiple times, but each instance the instance name, callsign, must be unique. |
References
Ref ID | Description |
---|---|
HTTP | HTTP specification |
JSON-RPC | JSON-RPC 2.0 specification |
JSON | JSON specification |
Thunder | Thunder API Reference |
Description
TimeZone JSON-RPC interface.
This interface uses legacy
lowercase
naming convention. With the next major release the naming convention will change tocamelCase
.
Properties
The following properties are provided by the TimeZone interface:
TimeZone interface properties:
Property | R/W | Description |
---|---|---|
timezone | read/write | TimeZone for system |
timezone property
Provides access to the timeZone for system.
Value
Name | Type | M/O | Description |
---|---|---|---|
(property) | string | mandatory | TimeZone for system |
Example
Get Request
{
"jsonrpc": "2.0",
"id": 42,
"method": "<callsign>.1.timezone"
}
Get Response
{
"jsonrpc": "2.0",
"id": 42,
"result": "..."
}
Set Request
{
"jsonrpc": "2.0",
"id": 42,
"method": "<callsign>.1.timezone",
"params": "..."
}
Set Response
{
"jsonrpc": "2.0",
"id": 42,
"result": "null"
}
Notifications
Notifications are autonomous events triggered by the internals of the implementation and broadcasted via JSON-RPC to all registered observers. Refer to [Thunder] for information on how to register for a notification.
The following events are provided by the TimeZone interface:
TimeZone interface events:
Notification | Description |
---|---|
timezonechanged | TimeZone was set for the system |
timezonechanged notification
TimeZone was set for the system.
Notification Parameters
Name | Type | M/O | Description |
---|---|---|---|
params | string | mandatory | New TimeZone |
Example
Registration
{
"jsonrpc": "2.0",
"id": 42,
"method": "<callsign>.1.register",
"params": {
"event": "timezonechanged",
"id": "myid"
}
}
Notification
{
"jsonrpc": "2.0",
"method": "myid.timezonechanged",
"params": "..."
}
The client ID parameter is passed within the notification designator, i.e.
<client-id>.timezonechanged
.