Re: BEEP as OCP transport

[Marshall Rose <mrose@xxxxxxxxxxxxxxxx>]

> Did I miss anything?

i can't figure out half of what you're saying, because i gave you an
example with MSG and RPY, and you replied talking about MSG, ANS, and
NUL.
    
so, when i say:

    timeline 1					timeline 2
    ----------					----------
    C: MSG with some data & more-bit
    timeline 2 starts  
    					    S: RPY with some data & more-bit
    C: some data & more-bit		    S: some data & more-bit
    C: some data & more-bit		    S: some data & more-bit	
    C: some data & more-bit		    S: some data & more-bit
    C: some data & no more-bit		    S: some data & no more-bit
    
you seem to be replying that this won't work because you can't have more
than one message in flight on a single channel.
    
correct. so if the requirements is:
    
    - asynchronous request/response where the response can start coming
      back before the request is fully sent.
    
use the approach i explained above. if there is an additional
requirement that:
    
    - more than one simultaneous asynchronous request/response on a
      single beep session
    
then do each parallel exchange on its own channel.
    
if there are other requirements, or these requirements are wrong, let me
know.
    
/mtr