I have a ticketing process that is in need of queueing or pacing of actions. Because SEC is fairly efficient, it can process logs, deduplicate and generate tickets rather rapidly. It is fast enough that the ticket gateway can get swamped and tip over. As I see it, there are two things that need to happen to create a robust system: create a bigger receiver load handling capacity, implement receiver queueing, and implement transmitter queueing. The latter is what I am trying to address. Does anyone have a generalized solution that would allow to use an event store as a queue, with actions that would be dependent upon queue depth? How can SEC be configured to dampen bursts, but not necessarily throw away significant events?
Please advise, Tim Peiffer -- Tim Peiffer Network Support Engineer Office of Information Technology University of Minnesota/NorthernLights GigaPOP +1 612 626-7884 (desk) ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
