On 10/12/2010 5:42 PM, da...@lang.hm wrote:
> On Tue, 12 Oct 2010, Mark D. Nagel wrote:
>
>> I am looking at how to handle a case where rulesets will be applied to
>> multiple input sources (logical or actual) via jump, but those rulesets
>> may create and use context names and variables that would conflict
>> across those input sources.  How I have handled this prior to jump is
>> with multiple instances of SEC.  This works, of course, but with some
>> scalability problems depending on the number of partitions needed.  I
>> hoped to use jump to reduce that scalability problem, but this naming
>> conflict is not solved by jump.  What I think may be a good solution
>> would be to add a namespace option to the jump rule:
>
> why can't you make the context names unique? you can add whatever you
> would use as the namespace as part of the context name.
>

Because the rulesets themselves are general purpose and this would make
them more re-usable.  For example, consider a ruleset that scans for
Blackberry events.  It might create a bunch of contexts to store
information during processing, and those contexts are named based on
whatever scheme you come up with at the time to keep the names unique
within and across rulesets.  The rules are all dependent at runtime on
how those contexts are filled, etc.

Now I want to basically partition the input sources in some manner,
either based on input file(s) or based on some shared attribute of the
input stream.  Without unique naming for each partition, any one
partition's activity would affect the other (imagine a context set to
indicate something happened that another rule references, but this now
impacts processing in a different partition).  I want to apply that
ruleset to each partition, but I don't want just one instance of those
contexts -- I want one dedicated to each partition.  With the dynamic
namespace, you could easily re-use a ruleset via jump for lots of
different partitions without conflicts.

Regards,
Mark

-- 
Mark D. Nagel, CCIE #3177 <mna...@willingminds.com>
Principal Consultant, Willing Minds LLC (http://www.willingminds.com)
cell: 949-279-5817, desk: 714-495-4001, fax: 949-623-9854

*** Please send support requests to supp...@willingminds.com! *** 


------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Simple-evcorr-users mailing list
Simple-evcorr-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users

Reply via email to