Can be used to indicate which Content-Format is acceptable to the client.

A Attachable is a source or sink that can be attached to another source or sink.

Base class for MessageBuilder providing common implementation

Holds common data for IncomingRequest and OutgoingRequest

Base Implementation for ResourceHandler providing request not supported implementation for all resource handler.

Holds common data for IncomingResponse and OutgoingResponse

Abstract class extended from BaseResourceHandler with extra functionality to receive data from a request and forward it to subscribed Observers

Service to automate sending and receiving packets, this service can be exposed via remote api

Stack service for supporting blasting random packets over attached GG stack.

Uniquely identifies a Node with a bluetooth address that is connected over BLE

Creates a new BSD socket with given configuration data

Data representing address for both end of a BSD socket

Uniquely identifies a Node that is connected over BsdSocket

This interface is a specific subinterface of Parser that parses ByteArray objects

OutgoingBody with body source from a ByteArray

Coap Client/Server API.

Utility object for building a CoapEndpoint

Exception indicating error when requesting data from coap server

Contains all the configuration/flags used by CoAP endpoint handler registration

Provider for Endpoint that ensures only single CoapEndpoint instance exist per node

Exception thrown when ResponseCode for response from a CoAP request is ResponseCode.Class.clientError or ResponseCode.Class.serverError.

Service that sends CoAP requests using a CoAP endpoint

This class provides apis to setup/update CoAP request filters group #1 is used for non-authenticated connections, and group #0 (i.e. no filtering) is used for authenticated states.

Enum representing CoAP group filter mode CoAP resource filter can support up to four different filter groups.

Reusable cross-platform CoAP server that can be used for automated functionality and performance testing

The Content-Format Option indicates the representation format of the message payload.

Created by muyttersprot on 3/7/18.

Created by muyttersprot on 3/7/18.

Created by muyttersprot on 3/7/18.

Stack with Gattlink, a Network Interface, a UDP socket and DTLS

Resource handler to echo back any PUT and POST request

For option that does not have a value, like OptionNumber.IF_NONE_MATCH

Empty OutgoingBody

This class is the Client/Server API of that will be exposed to users of this library.

The request MAY include one or more ETag Options, identifying responses that the client has stored.

The Content-Format Option indicates the representation format of the message payload. These are the supported value for ContentFormatOption and AcceptOption coap options

Stack with only a Gattlink element.

This class holds general properties of the Golden Gate library like the logger, the GG Loop thread, etc.

The If-Match Option MAY be used to make a request conditional on the current existence or value of an ETag for one or more representations of the target resource.

The If-None-Match Option MAY be used to make a request conditional on the nonexistence of the target resource.

Creates a Tls key resolver with given key id and key data, mainly for test mode

Represents the body of a incoming coap message.

This interface represents incoming CoAP Message objects.

Incoming coap request message.

Incoming coap response message.

OutgoingBody with body source from a InputStream

Option value with Int type

The values of these options specify the location at which the resource was created. Otherwise, the resource was created at the request URI.

The values of these options specify the location at which the resource was created. Otherwise, the resource was created at the request URI.

Caches can use the Max-Age Option to determine freshness and (if present) the ETAG Option for validation

In-Memory DataSink that is intended to be used for testing

In-Memory DataSource that is intended to be used for testing

This interface represents CoAP message objects.

Supported Coap methods. These are analogous to HTTP methods of the same names.

Marker interface for uniquely identifying a remote Node device

Option value with Opaque type

Individual Coap option

Supported options that can be added to a coap message options

Supported value types for a coap option

Represents body of outgoing coap message.

This interface represents outgoing CoAP Message objects.

A MessageBuilder is used for constructing Message objects. This interface contains the shared components of OutgoingRequestBuilder and OutgoingResponseBuilder

Represents outgoing request for a request in coap client mode.

Concrete class of MessageBuilder for building OutgoingRequest

Implementations of this interface will be sent back to the CoAP Client in response to requests coming in to a CoAP Server

Concrete class of MessageBuilder for building OutgoingResponse

This can be used by the library to parse responses into a format the caller desires

A user of this API will implement this interface and register it with an Endpoint. The user can then expect each of these methods to be called when an appropriate request is received.

This represents a CoAP response code (analogous to an HTTP response code (e.g. 201, 404, 500)

RxSource is a DataSource for bottom on Golden Gate stack and DataSink for top of Native/Android connection Bridge and is used to receive data packets to GG stack from connected Node

StackService for sending single message over attached GG stack

Stack with Gattlink, a Network Interface, and a UDP socket

A Kotlin representation of a Golden Gate stack. The data sink and data source exposed through getAsDataSinkPointer and getAsDataSourcePointer are the data sink/source on the "top" of the stack.

Configuration in which GG stack should be created

Service that communicates with top of the stack

Vendor(Fitbit) option for start offset in a file

Option value with String type

Registry for all TlsKeyResolver, when resolving a keyId default TlsKeyResolver will be applied fist followed by any registered TlsKeyResolver in order they are registered

TxSink is a DataSink for bottom on Golden Gate stack and DataSource for top of Native/Android connection Bridge and is used to transmit data packets from GG stack to connected Node

Specifies one argument parameterizing the resource.

The native side of this class keeps a global reference to the instance on the C-side Remember to call cleanup() when it's no longer needed.