Multiple frame metadata and data application delivery undefined about rsocket HOT 3 CLOSED

Metadata and data encoding are defined in the SETUP frame and the discussion between metadata as a separate frame as opposed to within the same frame with data was discussed in issues #3 and #13

from rsocket.

MIME type behaviors are not defined in the spec. If you're going to specify this stuff inside Reactive Sockets, you need to define the behaviors.

If the metadata MIME type is audio/mpeg3 or text/plain then perhaps the metadata across multiple frames is simply concatenated together.

If the metadata MIME type is text/rfc822 then perhaps metadata across multiple frames should be last-frame-wins.

from rsocket.

@wmiaw I believe the easiest way to clarify this is that the (potentially reassembled) RESPONSE or request is an entire object with the MIME type. So, concat or last-object-wins is up to usage.

from rsocket.