- 02 7月, 2016 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit adds a Decoder#decodeOne() method in order to handle correctly the streaming versus one value deserialization based on the type provided by the user. For example, if a List parameter is provided in a controller method, Jackson will be called once, while if the user provides a Flux or an Observable parameter, Jackson will be called for each element.
-
- 01 7月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 10 6月, 2016 1 次提交
-
-
由 Arjen Poutsma 提交于
Renamed getSupportedMimeTypes() to getEncodableMimeTypes and getDecodableMimeTypes. This will allow for both Encoder and Decoder to be implemented in the same class. This issue fixes #113.
-
- 09 6月, 2016 1 次提交
-
-
由 Rossen Stoyanchev 提交于
-
- 22 4月, 2016 1 次提交
-
-
由 Arjen Poutsma 提交于
This commit introduces the AbstractSingleValueEncoder, an abstract base class for encoders that only handle a single value.
-
- 11 12月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
The tests demonstrate failures at various phases of request processing and the resulting error signals.
-
- 23 11月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
reactive.codec -> core.codec reactive.io -> util These may very well not be the final locations. For now they simply express that there are classes that belong somewhere in core, i.e. they are lower level dependencies than web.
-
- 14 11月, 2015 2 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Sebastien Deleuze 提交于
This commit introduces the following changes: - MessageToByteEncoder/Decoder renamed to Encoder/Decoder - JsonObjectEncoder/Decoder are now used directly in JacksonJsonEncoder/Decoder - Codec uses MimeType instead of MediaType since they are not specific to HTTP - Default MimeType are now managed thanks to Encoder/Decoder#getSupportedMimeTypes() - AbstractEncoder/Decoder takes care of generic MimeType related behavior
-
- 31 10月, 2015 1 次提交
-
- 29 10月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit introduces the following changes: - Publisher -> Observable/Stream/etc. conversion is now managed in a dedicated ConversionService instead of directly in RequestBodyArgumentResolver and ResponseBodyResultHandler - More isolated logic that decides if the stream should be serialized as a JSON array or not - Publisher<ByteBuffer> are now handled by regular ByteBufferEncoder and ByteBufferDecoder - Handle Publisher<Void> return value properly - Ensure that the headers are properly written even for response without body - Improve JsonObjectEncoder to autodetect JSON arrays
-
- 05 10月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
-
- 22 9月, 2015 1 次提交
-
-
由 Sebastien Deleuze 提交于
-
- 25 8月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Introduce http and dispatch packages under org.springframework.web to separate HTTP-specific adapter code from higher level web framework code. Move classes into their respective locations.
-
- 12 8月, 2015 1 次提交
-
-
由 Rossen Stoyanchev 提交于
This commit introduces HTTP request and response abstractions along with Servlet-based implementations similar to the ones in the http package of spring-web but using Reactive Streams. In turn HttpHandler now accepts the request and response types and returns Publisher<Void> that reflects the end of handling. The write method on the response also returns Publisher<Void> allowing deferred writing. At the moment however the underlying Servlet 3.1 support only supports a single publisher after which the connection is closed. Only simple byte[] is supported for reading and writing.
-
- 09 7月, 2015 1 次提交
-
-
由 Arjen Poutsma 提交于
-
- 07 7月, 2015 1 次提交
-
-
由 Arjen Poutsma 提交于
-