Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 11FA3200CC9 for ; Mon, 3 Jul 2017 05:14:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 10B43160BFE; Mon, 3 Jul 2017 03:14:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 56BB9160BEE for ; Mon, 3 Jul 2017 05:14:06 +0200 (CEST) Received: (qmail 95559 invoked by uid 500); 3 Jul 2017 03:14:05 -0000 Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@thrift.apache.org Delivered-To: mailing list dev@thrift.apache.org Received: (qmail 95548 invoked by uid 99); 3 Jul 2017 03:14:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jul 2017 03:14:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D2E8DC049F for ; Mon, 3 Jul 2017 03:14:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.011 X-Spam-Level: X-Spam-Status: No, score=-100.011 tagged_above=-999 required=6.31 tests=[SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ajXZQFCZtfOF for ; Mon, 3 Jul 2017 03:14:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A4DEC5FDF3 for ; Mon, 3 Jul 2017 03:14:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 9555FE0D39 for ; Mon, 3 Jul 2017 03:14:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id EB16F245E0 for ; Mon, 3 Jul 2017 03:14:00 +0000 (UTC) Date: Mon, 3 Jul 2017 03:14:00 +0000 (UTC) From: "taozle (JIRA)" To: dev@thrift.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (THRIFT-4236) Support context in go generated code. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 03 Jul 2017 03:14:07 -0000 [ https://issues.apache.org/jira/browse/THRIFT-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071878#comment-16071878 ] taozle commented on THRIFT-4236: -------------------------------- Awesome! I am considering making this the default behavior in 1.0, any advise? if this make sense, should i work for it now or after 0.11.0 released? > Support context in go generated code. > ------------------------------------- > > Key: THRIFT-4236 > URL: https://issues.apache.org/jira/browse/THRIFT-4236 > Project: Thrift > Issue Type: Improvement > Components: Go - Compiler, Go - Library > Reporter: taozle > Assignee: taozle > Fix For: 0.11.0 > > > Since context is widely used in go's community, and there is lots of advantage to use context such as control timeout, carry extra info in one request etc, so is there any plan for this? i just searched the issues but didn't find anything about this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)