Uses of Interface
info.sswap.api.http.HTTPResponse

Packages that use HTTPResponse
info.sswap.api.http Java API access to HTTP API 
info.sswap.impl.http   
 

Uses of HTTPResponse in info.sswap.api.http
 

Subinterfaces of HTTPResponse in info.sswap.api.http
static interface HTTPClient.RIGResponse
          Access to get an RIG on success or a network response object (via the superinterface) on failure.
static interface HTTPClient.RQGResponse
          Access to get an RQG on success or a network response object (via the superinterface) on failure.
static interface HTTPProvider.PDGResponse
          Exposes access to both a ready-to-use Provider Description Graph (PDG) on success or a network response object on failure.
static interface HTTPProvider.RDGResponse
          Exposes access to both a ready-to-use Resource Description Graph (RDG) on success or a network response object on failure.
static interface HTTPProvider.RRGResponse
          Exposes access to both a ready-to-use Resource Response Graph (RRG) on success or a network response object on failure.
 

Uses of HTTPResponse in info.sswap.impl.http
 

Classes in info.sswap.impl.http that implement HTTPResponse
 class AbstractHTTPResponse
          An AbstractHTTPResponse consists of a SSWAPDocument as the return pay load of an invocation, along with the network response object.
 class HTTPAPIImpl.PDGResponse
          Exposes access to both a ready-to-use PDG on success or a network response object on failure.
 class HTTPAPIImpl.RDGResponse
          Exposes access to both a ready-to-use RDG on success or a network response object on failure.
 class HTTPAPIImpl.RIGResponse
          Exposes access to both a ready-to-use RIG on success or a network response object on failure.
 class HTTPAPIImpl.RQGResponse
          Exposes access to both a ready-to-use RQG on success or a network response object on failure.
 class HTTPAPIImpl.RRGResponse
          Exposes access to both a ready-to-use RRG on success or a network response object on failure.
 



Copyright (c) 2011, iPlant Collaborative, University of Arizona, Cold Spring Harbor Laboratories, University of Texas at Austin.