2362N/A * Copyright (c) 1997, 2002, Oracle and/or its affiliates. All rights reserved. 0N/A * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 0N/A * This code is free software; you can redistribute it and/or modify it 0N/A * under the terms of the GNU General Public License version 2 only, as 2362N/A * published by the Free Software Foundation. Oracle designates this 0N/A * particular file as subject to the "Classpath" exception as provided 2362N/A * by Oracle in the LICENSE file that accompanied this code. 0N/A * This code is distributed in the hope that it will be useful, but WITHOUT 0N/A * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 0N/A * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 0N/A * version 2 for more details (a copy is included in the LICENSE file that 0N/A * accompanied this code). 0N/A * You should have received a copy of the GNU General Public License version 0N/A * 2 along with this work; if not, write to the Free Software Foundation, 0N/A * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 2362N/A * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 2362N/A * or visit www.oracle.com if you need additional information or have any 0N/A * An interface for events that know how to dispatch themselves. 0N/A * By implementing this interface an event can be placed upon the event 0N/A * queue and its <code>dispatch()</code> method will be called when the event 0N/A * is dispatched, using the <code>EventDispatchThread</code>. 0N/A * This is a very useful mechanism for avoiding deadlocks. If 0N/A * a thread is executing in a critical section (i.e., it has entered 0N/A * one or more monitors), calling other synchronized code may 0N/A * cause deadlocks. To avoid the potential deadlocks, an 0N/A * <code>ActiveEvent</code> can be created to run the second section of 0N/A * code at later time. If there is contention on the monitor, 0N/A * the second thread will simply block until the first thread 0N/A * has finished its work and exited its monitors. 0N/A * For security reasons, it is often desirable to use an <code>ActiveEvent</code> 0N/A * to avoid calling untrusted code from a critical thread. For 0N/A * instance, peer implementations can use this facility to avoid 0N/A * making calls into user code from a system thread. Doing so avoids 0N/A * potential deadlocks and denial-of-service attacks. 0N/A * @author Timothy Prinzing 0N/A * Dispatch the event to its target, listeners of the events source, 0N/A * or do whatever it is this event is supposed to do.