[ 
https://issues.apache.org/jira/browse/DISPATCH-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078269#comment-16078269
 ] 

ASF GitHub Bot commented on DISPATCH-767:
-----------------------------------------

Github user alanconway commented on a diff in the pull request:

    https://github.com/apache/qpid-dispatch/pull/172#discussion_r126155845
  
    --- Diff: include/qpid/dispatch/message.h ---
    @@ -203,9 +203,9 @@ int  qd_message_get_phase_annotation(const qd_message_t 
*msg);
     void qd_message_set_ingress_annotation(qd_message_t *msg, 
qd_composed_field_t *ingress_field);
     
     /**
    - * Receive message data via a delivery.  This function may be called more 
than once on the same
    - * delivery if the message spans multiple frames.  Once a complete message 
has been received, this
    - * function shall return the message.
    + * Receive message data frame by frame via a delivery.  This function may 
be called more than once on the same
    + * delivery if the message spans multiple frames. Always returns a 
message. The message buffers are filled up to the point with the data that was 
been received so far.
    + * The buffer keeps filling up on successive calls to this function.
      *
      * @param delivery An incoming delivery from a link
      * @return A pointer to the complete message or 0 if the message is not 
yet complete.
    --- End diff --
    
    This comment is out of date


> Message Cut-Through/Streaming for efficient handling of large messages
> ----------------------------------------------------------------------
>
>                 Key: DISPATCH-767
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-767
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Router Node
>            Reporter: Ted Ross
>            Assignee: Ganesh Murthy
>             Fix For: 1.0.0
>
>
> When large, multi-frame messages are sent through the router, there is no 
> need to wait for the entire message to arrive before starting to send it 
> onward.
> This feature causes the router to route the first frame and allow subsequent 
> frames in a delivery to be streamed out in pipeline fashion.  Ideally, the 
> memory usage in the router should only involve pending frames.  This would 
> allow the router to handle arbitrary numbers of concurrent arbitrarily large 
> messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to