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

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

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

    https://github.com/apache/qpid-dispatch/pull/177#discussion_r129318215
  
    --- Diff: src/message_private.h ---
    @@ -107,11 +106,21 @@ typedef struct {
         qd_parsed_field_t   *ma_pf_to_override;
         qd_parsed_field_t   *ma_pf_trace;
         int                  ma_int_phase;
    +    //qd_parsed_field_t   *parsed_message_annotations;
    +
    +    bool                 discard;                        // Should this 
message be discarded?
    +    bool                 receive_complete;               // true if the 
message has been completely received, false otherwise
    +    unsigned int         fanout;                         // The number of 
receivers for this message. This number does not include in-process subscribers.
     } qd_message_content_t;
     
     typedef struct {
         DEQ_LINKS(qd_message_t);   // Deque linkage that overlays the 
qd_message_t
    -    qd_message_content_t *content;
    +    qd_field_location_t   cursor;          // A pointer to the current 
location of the outgoing byte stream.
    --- End diff --
    
    qd_iterator_pointer_t might be more appropriate for a pointer into buffers. 
field_location has baggage that is not needed.


> 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