| Interface and Description |
|---|
| com.spotify.apollo.Serializer
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 |
|---|
| com.spotify.apollo.serialization.AutoSerializer
the new preferred way to do response serialization is via a
Middleware,
see Serializer. |
| com.spotify.apollo.serialization.JsonSerializer
the new preferred way to do response serialization is via a
Middleware,
see Serializer. |
| com.spotify.apollo.Payloads
the new preferred way to do response serialization is
via a
Middleware, see Serializer. |
| com.spotify.apollo.serialization.RawSerializer
the new preferred way to do response serialization is via a
Middleware,
see Serializer. |
| com.spotify.apollo.serialization.StringSerializer
the new preferred way to do response serialization is via a
Middleware,
see Serializer. |
Copyright © 2016. All rights reserved.