Return-Path: Delivered-To: apmail-incubator-uima-user-archive@locus.apache.org Received: (qmail 22293 invoked from network); 29 Aug 2007 16:06:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2007 16:06:19 -0000 Received: (qmail 92790 invoked by uid 500); 29 Aug 2007 16:06:14 -0000 Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org Received: (qmail 92769 invoked by uid 500); 29 Aug 2007 16:06:14 -0000 Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: uima-user@incubator.apache.org Delivered-To: mailing list uima-user@incubator.apache.org Received: (qmail 92760 invoked by uid 99); 29 Aug 2007 16:06:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 09:06:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [141.142.2.177] (HELO zanamavir.ncsa.uiuc.edu) (141.142.2.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 16:06:09 +0000 Received: from candy.ncsa.uiuc.edu (candy.ncsa.uiuc.edu [141.142.220.49]) by zanamavir.ncsa.uiuc.edu (8.14.0/8.14.0) with ESMTP id l7TG5kL7030358; Wed, 29 Aug 2007 11:05:46 -0500 Message-Id: <7.0.0.16.2.20070829102140.04b5dc60@ncsa.uiuc.edu> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Wed, 29 Aug 2007 11:05:45 -0500 To: uima-user@incubator.apache.org From: Andrew Shirk Subject: read/write resource sharing Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Null-Tag: 1b399f78efc802c0ec82bca5f66b2c8b X-NCSA-MailScanner-Information: Please contact help@ncsa.uiuc.edu for more information, zanamavir.ncsa.uiuc.edu X-NCSA-MailScanner: Found to be clean X-Virus-Checked: Checked by ClamAV on apache.org What is the best practice for sharing read/write resources amongst analysis engines in an aggregate? For example, say you have an annotator early in a flow that reads a configuration file off disk in order determine its behavior. Then, the next annotator does something, and needs to write changes to the configuration file so that another annotator downstream, whose behavior is also determined by the contents of the configuration file, can read in the resource that contains the changes. Does this make sense? Any help or ideas would be appreciated. I can think of some ugly hacks, but it would be nice to know if I'm missing some portion of the API that supports this type of scenario. Thanks, Andrew