You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/03/20 23:25:43 UTC
[jira] [Commented] (TS-2652) atscppapi: Allow developers to cancel
AsyncHttpFetch in specific and AsyncProviders in general
[ https://issues.apache.org/jira/browse/TS-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942416#comment-13942416 ]
ASF GitHub Bot commented on TS-2652:
------------------------------------
GitHub user manjeshnilange opened a pull request:
https://github.com/apache/trafficserver/pull/65
Patch for TS-2652: Allowing cancelation of AsyncProviders
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/manjeshnilange/trafficserver master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/65.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #65
----
commit af12e778714f6950316d2752339be178df43d7f1
Author: Manjesh Nilange <ma...@yahoo.com>
Date: 2014-03-20T22:22:52Z
Patch for TS-2652: Allowing cancelation of AsyncProviders
----
> atscppapi: Allow developers to cancel AsyncHttpFetch in specific and AsyncProviders in general
> ----------------------------------------------------------------------------------------------
>
> Key: TS-2652
> URL: https://issues.apache.org/jira/browse/TS-2652
> Project: Traffic Server
> Issue Type: Wish
> Reporter: Manjesh Nilange
> Assignee: Brian Geffon
>
> Use case - if a plugin starts an async http fetch but wants to cancel it before completion (timeout or something), the options available today are
> 1) setting some state in the plugin and using this to ignore the callback.
> 2) delete receiver (most cases a transaction plugin).
> #1 is ugly and #2 is not possible always (there may be other things the plugin wants to do).
--
This message was sent by Atlassian JIRA
(v6.2#6252)