A classe Receiver representa o destinatário do e-mail.
The Receiver interface is an important internal interface within Saxon, and provides a powerful mechanism for integrating Saxon with other applications. It has been designed with extensibility and stability in mind. However, it should be considered as an interface designed primarily for internal use, and not as a completely stable part of the public Saxon API.
@author Michael H. Kay
ReceiverCollection. A receiver represents a static area shaped object that can have different socalled sensitivites for different locations inside its bounding area. The Receiver interface is a general description of a receiver, giving it a name and bounds and providing a method for querying sensitivities as a function of a point in 2D-space. Additional methods deal with data storage (set/getDirectory) and GUI display (getOutline).
All coordinates are defined for the virtual space (0,0) ... (1,1) @author Hanns Holger Rutz @version 0.75, 10-Jun-08 @see de.sciss.meloncillo.session.SessionCollection @see de.sciss.meloncillo.gui.VirtualSurface
Receiver receives {@link MidiEvent} objects and typically does something useful in response, such as interpreting them to generate sound or raw MIDI output. Common MIDI receivers include synthesizers and MIDI Out ports.
@see MidiDevice
@see Synthesizer
@see Transmitter
@author Kara Kytle
The Receiver interface is an important internal interface within Saxon, and provides a powerful mechanism for integrating Saxon with other applications. It has been designed with extensibility and stability in mind. However, it should be considered as an interface designed primarily for internal use, and not as a completely stable part of the public Saxon API.
@author Michael H. Kay
Just as Appenders send logging events outside of the log4j environment (to files, to smtp, to sockets, etc), Receivers bring logging events inside the log4j environment.
Receivers are meant to support the receiving of remote logging events from another process. For example, SocketAppender "appends" a logging event to a socket, configured for a specific host and port number. On the receiving side of the socket can be a SocketReceiver object. The SocketReceiver object receives the logging event, and then "posts" it to the log4j environment (LoggerRepository) on the receiving machine, to be handled by the configured appenders, etc. The various settings in this environment (Logger levels, Appender filters & thresholds) are applied to the received logging event.
Receivers can also be used to "import" log messages from other logging packages into the log4j environment.
Receivers can be configured to post events to a given LoggerRepository.
Subclasses of Receiver must implement the isActive(), activateOptions(), and shutdown() methods. The doPost() method is provided to standardize the "import" of remote events into the repository.
@author Mark Womack
@author Ceki Gülcü
@author Paul Smith
{@link Receiver} is responsible for receiving an event to a {@link ProcessingElement} instance using a hashKey.
A Listener implementation receives data from the network and passes an event as a byte array to the {@link Receiver}. The byte array is de-serialized and converted into an {@link Event}. Finally the event is passed to the matching streams.
There is a single {@link Receiver} instance per node.Details on how the cluster is partitioned and how events are serialized and transmitted to its destination are hidden from the application developer. The difference between a Receiver and an {@link Acceptor} is that anAcceptor can choose to reject the value handed to it.
@author Torgil Zethson
@since 3.0.0
The Receiver interface is an important internal interface within Saxon, and provides a powerful mechanism for integrating Saxon with other applications. It has been designed with extensibility and stability in mind. However, it should be considered as an interface designed primarily for internal use, and not as a completely stable part of the public Saxon API.
@author Michael H. Kay
Receiver is class used for receiving PDUs from SMSC. It can be used two ways: it has methods for synchronous (blocking) receiving of PDUs and as it is derived from ReceiverBase whic on turn is derived from ProcessingThread class, it can also receive PDUs on background and puts them into a queue.
@author Logica Mobile Networks SMPP Open Source Team
@version $Revision: 1.2 $
@see ReceiverBase
@see Connection
@see Session
@see Queue
All implementations of this interface must follow these rules, regardless of the number of threads that are accessing the receiver:
Objects that implement this interface can only be contained by an instance of IOPort. @author Jie Liu, Edward A. Lee, Lukito Muliadi @version $Id: Receiver.java,v 1.66 2006/06/17 14:27:40 eal Exp $ @since Ptolemy II 0.2 @Pt.ProposedRating Green (eal) @Pt.AcceptedRating Green (bart) @see Token
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |