Interface for attaching authentication information to a web query.
Query listener interface.
Executes an HTTP DELETE operation.
Executes an HTTP GET operation.
Executes an HTTP POST operation.
Executes an HTTP PUT operation.
Abstract base class for web queries.
Query status codes.
Represents a collection of keyed data associated with a query.
Query listener adapter.
Supported HTTP methods.
Thrown when an error occurs while executing a web query.
Provides classes for communicating with HTTP-based web services.
Fundamentally, a web query is simply an HTTP request. However, the default data format used by a web query is not HTML, but JSON. This allows a caller to effectively invoke database-like operations over the web - the HTTP methods are used in a manner that is very similar to their corresponding SQL equivalents:
|HTTP Method||SQL Query||Behavior|
These operations, sometimes referred to as "CRUD", form the basis of the Representational State Transfer (REST) model of building web services. Pivot web queries are designed primarily to facilitate interaction with JSON-based REST services. However, they are sufficiently generic to support communication with any type of HTTP-based service, using any data format (for example, XML). This enables web queries to be used in a broad range of server communication scenarios.