Return-Path: Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org Received: (qmail 74033 invoked from network); 3 Apr 2008 10:06:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Apr 2008 10:06:29 -0000 Received: (qmail 78206 invoked by uid 500); 3 Apr 2008 10:06:30 -0000 Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org Received: (qmail 78187 invoked by uid 500); 3 Apr 2008 10:06:29 -0000 Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-user@activemq.apache.org Delivered-To: mailing list camel-user@activemq.apache.org Received: (qmail 78178 invoked by uid 99); 3 Apr 2008 10:06:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 03:06:29 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2008 10:05:38 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JhMKU-0000V6-1S for camel-user@activemq.apache.org; Thu, 03 Apr 2008 03:05:58 -0700 Message-ID: <16467369.post@talk.nabble.com> Date: Thu, 3 Apr 2008 03:05:58 -0700 (PDT) From: fuchsmi To: camel-user@activemq.apache.org Subject: Aggregation with idle timeouts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: michael.fuchs@fatwire.com X-Virus-Checked: Checked by ClamAV on apache.org Hi all, It looks like camel rocks and it a great framework for our project. Anyway, one feature we need is to aggregate based on a groupid with an timeout. To give an simple example, every hit of a visitor of an website is one message, its sessionid is the groupid. so we aggragate based on the users sessionid. now we want to finish the aggragation after the user is 30 minutes idle. Is it possible to implement that based on the Aggragator pattern? Is there an existing implementation of a functionallity like this? -- View this message in context: http://www.nabble.com/Aggregation-with-idle-timeouts-tp16467369s22882p16467369.html Sent from the Camel - Users mailing list archive at Nabble.com.