Untangling events


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Untangling events
# 1  
Old 12-25-2008
Untangling events

by: Philip Howard,* Bloor Research Complex event processing, business event processing, security event management, log management, data retention systems, event-driven architecture, event warehousing: are these topics and other related ones all subsets of what is essentially a single market or are they distinct markets? In this and the following series of articles I will attempt to [...]

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. AIX

Auditing events

Hi there, I want to enable auditing for the following events in a critical AIX UNIX server by editing the /etc/syslog.conf file: Authentication events (login success, login failure, logout) Privilege use events (change to another user etc.) ... (1 Reply)
Discussion started by: venksel
1 Replies
Login or Register to Ask a Question
XSelectInput(3) 						  XLIB FUNCTIONS						   XSelectInput(3)

NAME
XSelectInput - select input events SYNTAX
int XSelectInput(Display *display, Window w, long event_mask); ARGUMENTS
display Specifies the connection to the X server. event_mask Specifies the event mask. w Specifies the window whose events you are interested in. DESCRIPTION
The XSelectInput function requests that the X server report the events associated with the specified event mask. Initially, X will not report any of these events. Events are reported relative to a window. If a window is not interested in a device event, it usually propa- gates to the closest ancestor that is interested, unless the do_not_propagate mask prohibits it. Setting the event-mask attribute of a window overrides any previous call for the same window but not for other clients. Multiple clients can select for the same events on the same window with the following restrictions: o Multiple clients can select events on the same window because their event masks are disjoint. When the X server generates an event, it reports it to all interested clients. o Only one client at a time can select CirculateRequest, ConfigureRequest, or MapRequest events, which are associated with the event mask SubstructureRedirectMask. o Only one client at a time can select a ResizeRequest event, which is associated with the event mask ResizeRedirectMask. o Only one client at a time can select a ButtonPress event, which is associated with the event mask ButtonPressMask. The server reports the event to all interested clients. XSelectInput can generate a BadWindow error. DIAGNOSTICS
BadWindow A value for a Window argument does not name a defined Window. SEE ALSO
Xlib - C Language X Interface X Version 11 libX11 1.2.1 XSelectInput(3)