Class and Description |
---|
Client
An Apollo service client.
|
Environment
An interface that an application can use to interact with the execution
environment of an Apollo application.
|
Environment.RoutingEngine |
Request
Defines the data Apollo presents for an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Serializer.Payload
Deprecated.
|
Status
Lists more-or-less common status codes, taken from
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html.
|
Status.WithReasonPhrase |
StatusType
Definition of a type for HTTP status codes.
|
StatusType.Family
Defines classes of status codes as described in
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html, using the name Family since 'class'
is overloaded in Java.
|
Class and Description |
---|
RequestContext
This object contains all the needed information related to an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Class and Description |
---|
AppInit
An application initializer that will set up the application using an
Environment . |
Client
An Apollo service client.
|
Environment
An interface that an application can use to interact with the execution
environment of an Apollo application.
|
Environment.RoutingEngine |
Request
Defines the data Apollo presents for an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Class and Description |
---|
AppInit
An application initializer that will set up the application using an
Environment . |
Class and Description |
---|
Request
Defines the data Apollo presents for an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Serializer
Deprecated.
This interface is deprecated; the new preferred way to do response serialization is
via a
Middleware that converts the response object into a Response .
The reasons for preferring a Middleware are:
- This interface is not typesafe, whereas Middlewares can be. This means the compiler can help
you spot mistakes. Simply define your Middleware as a function from something like AsyncHandler<MyDomainObject> to AsyncHandler<Response<ByteString>> .
- Middlewares are more powerful; they can directly set headers and can also modify other things
on the Response, such as status codes and reason phrases. |
Serializer.Payload
Deprecated.
|
Class and Description |
---|
Client
An Apollo service client.
|
Request
Defines the data Apollo presents for an incoming request.
|
RequestContext
This object contains all the needed information related to an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Class and Description |
---|
Request
Defines the data Apollo presents for an incoming request.
|
RequestContext
This object contains all the needed information related to an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Serializer
Deprecated.
This interface is deprecated; the new preferred way to do response serialization is
via a
Middleware that converts the response object into a Response .
The reasons for preferring a Middleware are:
- This interface is not typesafe, whereas Middlewares can be. This means the compiler can help
you spot mistakes. Simply define your Middleware as a function from something like AsyncHandler<MyDomainObject> to AsyncHandler<Response<ByteString>> .
- Middlewares are more powerful; they can directly set headers and can also modify other things
on the Response, such as status codes and reason phrases. |
Class and Description |
---|
Request
Defines the data Apollo presents for an incoming request.
|
Serializer
Deprecated.
This interface is deprecated; the new preferred way to do response serialization is
via a
Middleware that converts the response object into a Response .
The reasons for preferring a Middleware are:
- This interface is not typesafe, whereas Middlewares can be. This means the compiler can help
you spot mistakes. Simply define your Middleware as a function from something like AsyncHandler<MyDomainObject> to AsyncHandler<Response<ByteString>> .
- Middlewares are more powerful; they can directly set headers and can also modify other things
on the Response, such as status codes and reason phrases. |
Serializer.Payload
Deprecated.
|
Class and Description |
---|
AppInit
An application initializer that will set up the application using an
Environment . |
Client
An Apollo service client.
|
Request
Defines the data Apollo presents for an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Class and Description |
---|
Request
Defines the data Apollo presents for an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
Class and Description |
---|
Request
Defines the data Apollo presents for an incoming request.
|
Response
Defines the data Apollo needs to construct and send a response to an incoming request.
|
StatusType
Definition of a type for HTTP status codes.
|
StatusType.Family
Defines classes of status codes as described in
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html, using the name Family since 'class'
is overloaded in Java.
|
Copyright © 2016. All rights reserved.