frames. Subsequent demand is signaled via REQUEST_N frames. Each side may also send metadata notifications, via the METADATA_PUSH frame, that do not pertain to any individual request but rather to the connection whole. Message Format RSocket messages contain data and metadata. Metadata can be used to send a route, a security token, etc. Data and metadata can be formatted differently. Mime types for each are declared SETUP frame and apply to all requests on a given connection. While all messages can have metadata, typically metadata such as a route are per-request and therefore only included in the first message on a

.............................................................................. 67 5.10.2. Using metadata-driven auto-proxying ....................................................................... 68 ........ 87 8. Source Level Metadata Support .................................................................................................... 8.1. Source-level metadata ........................... .............................................................................. 88 8.2. Spring's metadata support .......................................................................................

.............................................................................. 66 5.10.2. Using metadata-driven auto-proxying ....................................................................... 67 ........ 86 8. Source Level Metadata Support .................................................................................................... 8.1. Source-level metadata ........................... .............................................................................. 87 8.2. Spring's metadata support .......................................................................................

① Inject target handlers and the handler mapping for controllers. ② Prepare the request mapping metadata. ③ Get the handler method. ④ Add the registration. Kotlin @Configuration class MyConfig { ① Inject target handlers and the handler mapping for controllers. ② Prepare the request mapping metadata. ③ Get the handler method. ④ Add the registration. 33 1.4.3. Handler Methods Web MVC @RequestMapping String handle(@RequestPart("meta-data") Part metadata, ① @RequestPart("file-data") FilePart file) { ② // ... } ① Using @RequestPart to get the metadata. ② Using @RequestPart to get the file.

BeanPostProcessors ................................................... 70 3.7.2. Customizing configuration metadata with BeanFactoryPostProcessors ............... 72 3.7.3. Customizing instantiation logic using FactoryBeans .............................................................................. 152 7.9.2. Using metadata-driven auto-proxying ................................................................. 154 The ................................................................ 361 20.3.2. Using source-Level metadata ............................................................................ 361 20.3.3. Using JDK

.............................................................................. 67 5.10.2. Using metadata-driven auto-proxying ....................................................................... 69 ........ 93 8. Source Level Metadata Support .................................................................................................... 8.1. Source-level metadata ........................... .............................................................................. 94 8.2. Spring's metadata support .......................................................................................

BeanPostProcessors ................................................... 72 3.7.2. Customizing configuration metadata with BeanFactoryPostProcessors ............... 75 3.7.3. Customizing instantiation logic using FactoryBeans .............................................................................. 159 7.9.2. Using metadata-driven auto-proxying ................................................................. 161 7.10 ................................................................ 375 20.3.2. Using source-Level metadata ............................................................................ 375 20.3.3. Using JDK

BeanPostProcessors ................................................... 73 3.7.2. Customizing configuration metadata with BeanFactoryPostProcessors ............... 75 3.7.3. Customizing instantiation logic using FactoryBeans .............................................................................. 157 7.9.2. Using metadata-driven auto-proxying ................................................................. 159 7.10 ................................................................ 371 20.3.2. Using source-Level metadata ............................................................................ 371 20.3.3. Using JDK

.............................................................................. 76 6.10.2. Using metadata-driven auto-proxying ....................................................................... 77 ....... 100 9. Source Level Metadata Support .................................................................................................... 9.1. Source-level metadata ........................... ............................................................................. 102 9.2. Spring's metadata support .......................................................................................

.............................................................................. 87 6.10.2. Using metadata-driven auto-proxying ....................................................................... 88 ..... 111 9. Source Level Metadata Support .................................................................................................... 113 9.1. Source-level metadata ......................... ............................................................................. 113 9.2. Spring's metadata support .......................................................................................