[ 
https://issues.apache.org/jira/browse/TS-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Ben Zakai updated TS-4523:
--------------------------------
    Description: 
It would be nice to be able to pause/resume the data consumption in the 
Transformation Plugin.

My Own Use case:
I'm writing the data into a file, when it reaches a certain size I'd like to 
produce the file output for the downstream, while doing so I'd like to avoid 
reading more data from the upstream.
So the flow would be:
consume -> write into a file (K times)
file reaches X KB ?
  pause upstream socket
  produce data from file
  resume

  was:
It would be nice to be able to pause/resume the data consumption in the 
Transformation Plugin.

My Own Use case:
I'm writing the data into a file, when it reaches a certain size I'd like to 
produce the file output for the downstream, while doing so I'd like to avoid 
reading more data from the upstream.
So the flow would be:
consume -> write into a file x N times
file reaches X KB ? -> pause upstream socket, produce data from file and then 
resume


> Add the ability to pause/resume data consumption in the CPP API
> ---------------------------------------------------------------
>
>                 Key: TS-4523
>                 URL: https://issues.apache.org/jira/browse/TS-4523
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Plugins
>            Reporter: David Ben Zakai
>            Assignee: Uri Shachar
>             Fix For: 7.0.0
>
>
> It would be nice to be able to pause/resume the data consumption in the 
> Transformation Plugin.
> My Own Use case:
> I'm writing the data into a file, when it reaches a certain size I'd like to 
> produce the file output for the downstream, while doing so I'd like to avoid 
> reading more data from the upstream.
> So the flow would be:
> consume -> write into a file (K times)
> file reaches X KB ?
>   pause upstream socket
>   produce data from file
>   resume



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to