From user-return-5565-apmail-storm-user-archive=storm.apache.org@storm.apache.org Mon Dec 15 08:20:12 2014 Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5656691C0 for ; Mon, 15 Dec 2014 08:20:12 +0000 (UTC) Received: (qmail 32269 invoked by uid 500); 15 Dec 2014 08:20:11 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 32222 invoked by uid 500); 15 Dec 2014 08:20:11 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 32212 invoked by uid 99); 15 Dec 2014 08:20:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 08:20:11 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of idan.frid@gmail.com designates 209.85.212.180 as permitted sender) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2014 08:19:46 +0000 Received: by mail-wi0-f180.google.com with SMTP id n3so8142572wiv.1 for ; Mon, 15 Dec 2014 00:19:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=j4BXGG59RKg1iObSY1wP/elUeFbu06S9B752ZANLjrE=; b=EKme8bQb4xWsJafNH21wmja1/5cttT9cePYcvZHFdwgOlfCfjPO9cRoBCJZcGJ7ECa gCRMJa24WPGVMwBEdgKAzRqeNj6VQ6BxEiYw00sEoNZDVF8BnGrksmraIpN1gNzBP+7g lq+LqxVZawTfGREIdxtFiI4umkMXns2G/KbYks1pSuu74fomN6yA0xcetbq74575HZsV tWFHklqCCJ97Tu+cx0X2dGgfM6P+mHFiyHZVgo7P2HuzQFPz/UYgru7c7XUYSsDa4oy1 lRVN4wt/2aDloTghkb+Ht9SWCcO7bkviPlxVSAh12P3MGi4RfWHj/e4CCVtc950W3SGJ xBkA== MIME-Version: 1.0 X-Received: by 10.194.175.69 with SMTP id by5mr49130323wjc.32.1418631540629; Mon, 15 Dec 2014 00:19:00 -0800 (PST) Received: by 10.216.165.134 with HTTP; Mon, 15 Dec 2014 00:19:00 -0800 (PST) Date: Mon, 15 Dec 2014 10:19:00 +0200 Message-ID: Subject: Using AsyncHttpReuqest inside a Bolt From: Idan Fridman To: user@storm.apache.org Content-Type: multipart/alternative; boundary=089e013c60b80bebc9050a3ce5c9 X-Virus-Checked: Checked by ClamAV on apache.org --089e013c60b80bebc9050a3ce5c9 Content-Type: text/plain; charset=UTF-8 Hi All, My bolt need to dispatch async request to remote service. I am using AsyncHttpReuest library( https://github.com/AsyncHttpClient/async-http-client) which based on NIO channels to get the response asynchronously while not allocating Thread for each request. I was wondering if any side-effects could cause this implementation within Storm Bolt ? thank you. --089e013c60b80bebc9050a3ce5c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi All,
My bolt need to dispatch async reque= st to remote service.