Integration Types

Integration types are Quark data types that depend on using an integration to execute. Typically these types are defines with method signatures rather than code because the code needed to execute the desired functionality is specific to a particular integration and is defined within that integration. However, some integration types may include method definitions that use other integration types - these look like normal Quark data types but can’t be executed without an integration because of their dependencies. Essentially normal Quark data types can be used in code without installing an integration but integration types cannot. More information about the available integrations and how to install them can be found here.

Quark defines the following integration types:

Buffer

Documentation coming soon

Client

A factory class that can be used to create generic clients. Typically this class will be extended to define a more specific client for a particular application or service.

Codec

Documentation coming soon

HTTPHandler

Documentation coming soon

HTTPRequest

Documentation coming soon

HTTPResponse

Documentation coming soon

HTTPServlet

Documentation coming soon

JSONObject

Documentation coming soon

ResponseHolder

Holds a response while it is being formulated. This should only be used within types that are processing responses prior to their being sent to the client.

Runtime

Documentation coming soon

Server

A factory class that can be used to create generic servers. Typically this class will be extended to define a more specific server for a particular application or service.

Servlet

Documentation coming soon

Task

Documentation coming soon

WebSocket

Documentation coming soon

WSHandler

Documentation coming soon

WSServlet

Documentation coming soon