Jim,

-----Original Message-----
From: Jim Starkey [mailto:jas@...]
Sent: Monday, May 07, 2001 9:51 AM
To: IB-Architect@yahoogroups.com; IB-Architect@yahoogroups.com
Subject: RE: [IB-Architect] Re: Events Improvement

<snip>

In the original architecture (and, I believe, the current
implementation) the event table is in System V shared memory.
On most Unix systems, System V shared memory is implemented
in non-paged (i.e. real) memory. To minimize the amount of
memory required, the event manager was designed to track
only events for which an attached process has declared an
interest. Tracking only "interesting" events is no big deal.
However, with you wildcarding mechanism, any event that matches
an active wildcard must be tracked. Depending on the the
application, this might increased to number of events tracked
from a typical couple of dozen to hundreds of thousands,
millions, or more. If an application needs the functionality,
this may well be worth the cost. But the ramification on
configuration and limits of shared memory size should be
carefully explored.

<Sean>

Given the current cost of memory and 1Gb ram servers, it's the issue of
memory usage a red-herring?

Or is there some *nix limitation which I'm not aware of?

</Sean>