| Home >> All >> org >> activemq >> [ transport Javadoc ] |
Page 1 2 3
• org.activemq.transport: Javadoc index of package org.activemq.transport.
Package Samples:
• org.activemq.transport.activeio
• org.activemq.transport.composite
• org.activemq.transport.jabber
• org.activemq.transport.http
• org.activemq.transport.https
• org.activemq.transport.jrms
• org.activemq.transport.ember
• org.activemq.transport.ibmaio
• org.activemq.transport.jgroups
• org.activemq.transport.jxta
Classes:
• NetworkConnector: Represents a connector to one or more remote brokers. This class manages a number of NetworkChannel instances which may or may not be connected to a remote broker at any point in time. The implementation of this class could use a fixed number of configured NetworkChannel instances or could use discovery to find them.
• RemoteNetworkConnector: Represents a connector to one or more remote brokers. This class manages a number of NetworkChannel instances which may or may not be connected to a remote broker at any point in time. The implementation of this class could use a fixed number of configured NetworkChannel instances or could use discovery to find them.
• RemoteTransportChannel: A RemoteTransportChannel creates an embedded broker that creates a remote connection to another broker. This connection type is designed for reliable connections, that can use the storage mechansims of an embedded broker to be decoupled from the remote broker - i.e. for connections that need to be reliable, don't block but maybe using a transport across an unreliable network connection An example of the expected format is: remote://tcp://remotebroker:5060
• TransportChannel: A TransportChannel is used for tranporting packets between nodes e.g. a ActiveMQ JMS Connection and Broker. The TransportChannel supports synchronous and asynchronous send operations as well as sync or async reading of packets. A TransportChannel implementation could use a dedicated thread using blocking IO to read from a socket or could use NIO or poll some file system or database etc. On receipt of a Packet the TransportChannel should invoke the PacketListener
• PeerTransportChannel: A PeerTransportChannel creates an embedded broker and networks peers together to form a P-2-P network. By default, PeerTransportChannel uses discovery to locate other peers, and uses a well known service name on the discovery An example of the expected format is: peer://development.net where development.net is the service name used in discovery
• RemoteNetworkChannel: Represents a Boondocks broker's connection with a single remote broker which bridges the two brokers to form a network. The NetworkChannel contains a JMS connection with the remote broker. New subscriptions on the local broker are multiplexed into the JMS connection so that messages published on the remote broker can be replayed onto the local broker.
• NetworkChannel: Represents a broker's connection with a single remote broker which bridges the two brokers to form a network. The NetworkChannel contains a JMS connection with the remote broker. New subscriptions on the local broker are multiplexed into the JMS connection so that messages published on the remote broker can be replayed onto the local broker.
• DiscoveryTransportChannel: A org.activemq.transport.reliable.ReliableTransportChannel which uses a DiscoveryAgent to discover remote broker instances and dynamically connect to them.
• HttpServerTransportChannel: A server side HTTP based TransportChannel which processes incoming packets and adds outgoing packets onto a EDU.oswego.cs.dl.util.concurrent.Channel so that they can be dispatched by the HTTP GET requests from the client.
• SMLCGRandom: A Shuffled Multiple Combined Linear Congruential Generator Uses L'Ecuyer's CLCG4 with a Bays-Durham shuffle. From Numerical Recipes inC This produces a more random stream of results than just java.util.Random
• HttpClientTransportChannel: A HTTP org.activemq.transport.TransportChannel which uses the commons-httpclient library
• ZeroconfDiscoveryAgent: A org.activemq.transport.DiscoveryAgent using Zeroconf via the jmDNS library
• XStreamWireFormat: A org.activemq.io.WireFormat implementation which uses the XStream library to marshall commands onto the wire
• KeepAliveDaemon: KeepAliveDaemon keeps channels alive by sending KeepAlive packets on a specified interval. If the packets aren't don't get a receipt within a specified time, the channel will be forcefully disconnected.
• HttpTunnelServlet: A servlet which handles server side HTTP transport, delegaging to the ActiveMQ broker. This servlet is designed for being embedded inside an ActiveMQ Broker using an embedded Jetty or Tomcat instance.
• DiscoveryNetworkConnector: A NetworkConnector which uses discovery to find remote brokers to connect to
• NetworkMessageBridge: A NetworkMessageBridge consumes messages from a remote broker and daisy chains them to the local message producer, which will pass them into the local broker for consumption
• PeerTransportChannelFactory: Creates peer based transport. A PeerTransportChannel creates an embedded broker, and uses discovery and/or defined list of urls to create a p-2-p interconnected network.
• DiscoveryAgentSupport: A useful base class for DiscoveryAgent implementations
• ZeroconfTransportConnectorFactory: A Zeroconf implementation of a org.activemq.transport.TransportServerChannelFactory
• OpenWireFormatSupport: Base class for the code generated org.activemq.transport.openwire.io.OpenWireFormat
• HttpEmbeddedTunnelServlet: This servlet embeds an ActiveMQ broker inside a servlet engine which is ideal for deploying ActiveMQ inside a WAR and using this servlet as a HTTP tunnel.
• DiscoveryAgent: An agent used to discover other instances of a service. We typically use a discovery agent to auto-discover JMS clients and JMS brokers on a network
• ZeroconfTransportConnector: A Zeroconf implementation of org.activemq.transport.TransportServerChannel
• TransportServerChannel: Represents a Server which accepts incoming client connections in the form of TransportChannels which is used inside the JMS Broker
| Home | Contact Us | Privacy Policy | Terms of Service |