uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thilo Goetz <twgo...@gmx.de>
Subject Re: read/write resource sharing
Date Wed, 29 Aug 2007 16:18:17 GMT
If this happens often, one idea might be just to
stick the information in the CAS.  That way you
can even run several instances of this pipeline
and it will still work ;-)  Of course you're not
persisting the info that way, not sure if this is
a requirement or not.


Andrew Shirk wrote:
> 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

View raw message