Home >> All >> org >> activemq >> [ io Javadoc ]

•

org.activemq.io.impl.* (71)

•

org.activemq.io.util.* (21)

• org.activemq.io: Javadoc index of package org.activemq.io.


Package Samples:

• org.activemq.io.impl
• org.activemq.io.util

Classes:

• WireFormat: Represents a strategy of encoding packets on the wire or on disk using some kind of serialization or wire format. We use a default efficient format for Java to Java communication but other formats to other systems can be used, such as using simple text strings when talking to JavaScript or coming up with other formats for talking to C / C# languages or proprietary messaging systems we wish to interface with at the wire level etc.
• AbstractWireFormat: Represents a strategy of encoding packets on the wire or on disk using some kind of serialization or wire format. We use a default efficient format for Java to Java communication but other formats to other systems can be used, such as using simple text strings when talking to JavaScript or coming up with other formats for talking to C / C# languages or proprietary messaging systems we wish to interface with at the wire level etc.
• WireFormatLoader: Represents a strategy of encoding packets on the wire or on disk using some kind of serialization or wire format. We use a default efficient format for Java to Java communication but other formats to other systems can be used, such as using simple text strings when talking to JavaScript or coming up with other formats for talking to C / C# languages or proprietary messaging systems we wish to interface with at the wire level etc.
• TextWireFormat: Represents a text based WireFormat such as one that uses XML packets like the org.activemq.transport.xstream.XStreamWireFormat or the org.activemq.transport.jabber.JabberWireFormat
• DefaultWireFormat: This is a stateful AbstractDefaultWireFormat which implements value caching. Not optimal for use by many concurrent threads. One DefaultWireFormat is typically allocated per client connection.
• MemoryBoundedQueueManager: A factory manager for MemoryBoundedQueue and also ensures that the maximum memory used by all active MemoryBoundedQueues created by this instance stays within the memory usage bounds set.
• DataContainer: A DataContainer handles file persistence for a DiskBoundedQueue The DataContainer is a temporary data structure, that is only designed to exist for the lifetime of the application
• MemoryBoundedMessageCache: A simple cache that stores messages in memory. Cache entries are evicted when the memoryManager starts to run short on memory (A LRU cache is used).
• StatelessDefaultWireFormat: Provides a stateless implementation of AbstractDefaultWireFormat. Safe for use by multiple threads and incurs no locking overhead.
• ActiveMQMessageReaderTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
• ConsumerInfoReaderTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
• MessageAckReaderTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
• ProducerInfoReaderTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
• ReceiptReaderTest: To change the template for this generated type comment go to Window - Preferences - Java - Code Generation - Code and Comments
• AbstractDefaultWireFormat: Default implementation used for Java-Java protocols. When talking to non-Java nodes we may use a different wire format.
• SpooledBoundedActiveMQMessageQueue: Implements a controlled thread safe queue, with ActiveMQMessages being spooled to disk for reading asynchronously.
• ByteArray: Simple holder for a an array of Bytes - used instead of a ByteBuffer to avoid unecessary System.array() copies
• MemoryBoundedQueue: MemoryBoundedQueue is a queue bounded by memory usage for MemoryManageables
• WireByteArrayInputStream: Optimized ByteArrayInputStream that can be used more than once. Which is nice.
• AbstractPacketWriter: Allows instances implementing Packet interface to be serailized/deserailized
• PacketReader: Allows instances implementing Packet to read from a DataOutputStream
• AbstractPacketReader: Allows instances implementing Packet interface to be deserailized
• PacketWriter: Allows instances implementing Packet to written to a DataOutput
• CapacityInfoRequestReader: Reads a CapacityInfoRequest object from a Stream

Home | Contact Us | Privacy Policy | Terms of Service