-
betsy.bpel.virtual.common.Protocol
The {@link Protocol} is running on the host and offers several methods totell the server what has to be done next. This includes to send deployment instructions as well as to gather log files from the remote server.
@author Cedric Roeck
@version 1.0
-
cascading.lingual.catalog.Protocol
Class Protocol is an enhanced "enum" type that allows for runtime membership used for defining new "protocols" used during table and identifier runtime resolution.
-
com.alibaba.dubbo.rpc.Protocol
Protocol. (API/SPI, Singleton, ThreadSafe)
@author william.liangf
-
com.amazonaws.Protocol
-
com.betfair.cougar.api.export.Protocol
-
com.bj58.spat.gaea.protocol.sfp.v1.Protocol
版本一协义定义 1byte(版本号) | 4byte(协义总长度) | 4byte(序列号) | 1byte(服务编号) | 1byte(消息体类型) | 1byte 所采用的压缩算法 | 1byte 序列化规则 | 1byte 平台(.net java ...) | n byte消息体 | 5byte(分界符) 0 1~4 5~8 9 10 11 12 13 消息头总长度:14byte 协义总长度 = 消息头总长度 + 消息体总长度 (不包括分界符) 尾分界符: 9, 11, 13, 17, 18 版本号从ASCII > 48 开始标识
@author Service Platform Architecture Team (spat@58.com)
-
com.comphenix.protocol.PacketType.Protocol
-
com.compomics.util.pride.prideobjects.Protocol
-
com.digitalpebble.storm.crawler.protocol.Protocol
-
com.esri.gpt.control.webharvest.protocol.Protocol
Protocol.
-
com.icona.tree.nodes.Protocol
-
com.ning.http.client.ProxyServer.Protocol
-
com.peterhi.net.Protocol
-
com.sissi.protocol.Protocol
@author kim 2013-10-24
-
com.sleepycat.je.rep.elections.Protocol
Defines the request/response messages used in the implementation of elections. From Proposer to Acceptor: Propose -> Promise | Reject Accept -> Accepted | Reject From Proposer initiator to Learners: Result -> none The following exchange is not part of the elections process, but is used by the Monitor to query a Learner for the latest election result it's aware of, when the Monitor first starts up. From Monitor to Learner MasterQuery -> MasterQueryResponse | None
-
com.sleepycat.je.rep.stream.Protocol
Defines the messages used to set up a feeder-replica replication stream. From Feeder to Replica Heartbeat -> HeartbeatResponse Commit -> Ack Entry Note: in the future, we may want to support bulk entry messages From Replica to Feeder The following subset of messages represents the handshake protocol that precedes the transmission of replication log entries. ReplicaProtocolVersion -> FeederProtocolVersion | DuplicateNodeReject ReplicaJEVersions -> FeederJEVersions | JEVersions Reject MembershipInfo -> MembershipInfoOK | MembershipInfoReject SNTPRequest -> SNTPResponse Note that there may be multiple SNTPRequest/SNTPResponse message pairs that are exchanged as part of a single handshake. So a successful handshake requested sequence generated by the Replica looks like: ReplicaProtocolVersion ReplicaJEVersions MembershipInfo [SNTPRequest]+ The following messages constitute the syncup and the transmission of log entries. EntryRequest -> Entry | EntryNotFound | AlternateMatchpoint RestoreRequest -> RestoreResponse StartStream The Protocol instance has local state in terms of buffers that are reused across multiple messages. A Protocol instance is expected to be used in strictly serial fashion. Consequently, there is an instance for each Replica to Feeder connection, and two instances per Feeder to Replica connection: one for the InputThread and one for the OutputThread.
-
com.stimulus.archiva.domain.MailboxConnections.Protocol
-
com.sun.grizzly.Controller.Protocol
-
com.sun.grizzly.config.dom.Protocol
-
com.sun.midp.io.j2me.http.Protocol
-
com.thoughtworks.acceptance.someobjects.Protocol
@author
Jason van Zyl
@version $Id: Protocol.java 1345 2007-12-11 01:50:12Z joehni $
-
ecks.protocols.Protocol
Interface Protocol
Defines the interface that all protocol modules must work through.
@author Jeff Katz
-
net.nutch.protocol.Protocol
A retriever of url content. Implemented by protocol extensions.
-
net.sf.myway.gps.garmin.protocol.Protocol
This class handles the results comming from the unit.
@version $Revision: 1.1 $
@author andreas
-
net.spy.memcached.ConnectionFactoryBuilder.Protocol
-
net.windwards.dnsfrontend.api.Protocol
-
org.apache.avro.Protocol
A set of messages forming an application protocol.
A protocol consists of:
- a name for the protocol;
- an optional namespace, further qualifying the name;
- a list of types, or named {@link Schema schemas};
- a list of errors, or named {@link Schema schemas} for exceptions;
- a list of named messages, each of which specifies,
- request, the parameter schemas;
- one of either; or
- response, the response schema;
- errors, an optional list of potential error schema names.
-
org.apache.axis2.jaxws.message.Protocol
@version $Rev: 704201 $ $Date: 2008-10-13 14:52:25 -0400 (Mon, 13 Oct 2008) $
-
org.apache.commons.httpclient.protocol.Protocol
A class to encapsulate the specifics of a protocol. This class class also provides the ability to customize the set and characteristics of the protocols used.
One use case for modifying the default set of protocols would be to set a custom SSL socket factory. This would look something like the following:
Protocol myHTTPS = new Protocol( "https", new MySSLSocketFactory(), 443 ); Protocol.registerProtocol( "https", myHTTPS );
@author Michael Becke
@author Jeff Dever
@author
Mike Bowler
@since 2.0
-
org.apache.cxf.fediz.core.config.Protocol
-
org.apache.droids.api.Protocol
The protocol interface is a wrapper to hide the underlying implementation of the communication at protocol level.
@version 1.0
-
org.apache.geronimo.network.protocol.Protocol
@version $Rev: 46019 $ $Date: 2004-09-14 04:56:06 -0500 (Tue, 14 Sep 2004) $
-
org.apache.james.protocols.api.Protocol
Define a protocol
-
org.apache.logging.log4j.core.net.Protocol
-
org.apache.mailreaderjpa.Protocol
JPA entity class for the MAILREADER_PROTOCOLS
table.
-
org.apache.nutch.protocol.Protocol
A retriever of url content. Implemented by protocol extensions.
-
org.apache.oodt.cas.protocol.Protocol
Interface for communication over different transfer protocols
@author bfoster
@version $Revision$
-
org.apache.oodt.cas.pushpull.protocol.Protocol
@author bfoster
@version $Revision$
Protocol Interface Class
.
-
org.apache.qpid.server.model.Protocol
-
org.apache.savan.configuration.Protocol
-
org.asynchttpclient.ProxyServer.Protocol
-
org.brixcms.jcr.wrapper.BrixNode.Protocol
-
org.glassfish.admin.amx.intf.config.grizzly.Protocol
Note: attribute getters/setters are not included in this interface; use generic approach.
-
org.glassfish.grizzly.config.dom.Protocol
Defines one single high-level protocol like: http, https, iiop, etc.
-
org.glassfish.grizzly.http.Protocol
-
org.jacorb.orb.etf.ListenEndpoint.Protocol
-
org.jboss.as.clustering.jgroups.subsystem.Protocol
-
org.jclouds.trmk.vcloud_0_8.domain.Protocol
@author Everett Toews
-
org.jgroups.stack.Protocol
The Protocol class provides a set of common services for protocol layers. Each layer has to be a subclass of Protocol and override a number of methods (typically just
up()
,
Down
and
getName
. Layers are stacked in a certain order to form a protocol stack.
Events are passed from lower layers to upper ones and vice versa. E.g. a Message received by the UDP layer at the bottom will be passed to its higher layer as an Event. That layer will in turn pass the Event to its layer and so on, until a layer handles the Message and sends a response or discards it, the former resulting in another Event being passed down the stack.
Each layer has 2 FIFO queues, one for up Events and one for down Events. When an Event is received by a layer (calling the internal upcall ReceiveUpEvent
), it is placed in the up-queue where it will be retrieved by the up-handler thread which will invoke method Up
of the layer. The same applies for Events traveling down the stack. Handling of the up-handler and down-handler threads and the 2 FIFO queues is donw by the Protocol class, subclasses will almost never have to override this behavior.
The important thing to bear in mind is that Events have to passed on between layers in FIFO order which is guaranteed by the Protocol implementation and must be guranteed by subclasses implementing their on Event queuing.
Note that each class implementing interface Protocol MUST provide an empty, public constructor !
-
org.jibx.ws.protocol.Protocol
Provides an interface for creating a processor specific to a messaging protocol.
@author Nigel Charman
-
org.jivesoftware.util.Protocol
te an XMPP packet PacketCollector collector = connection.createPacketCollector(new PacketIDFilter()); connection.sendPacket(packet); Packet reply = collector.nextResult(); } public void testMethod() { // create protocol Protocol protocol = new Protocol(); // create mocked connection Connection connection = ConnectionUtils.createMockedConnection(protocol, "user@xmpp-server", "xmpp-server"); // add reply packet to protocol Packet reply = new Packet(); protocol.add(reply); // call method to test methodToTest(); // verify protocol protocol.verifyAll(); } Additionally to adding the response to the protocol instance you can pass verifications that will be executed when {@link #verifyAll()} is invoked.(See {@link Verification} for more details.)
If the {@link #printProtocol} flag is set to true {@link #verifyAll()} willalso print out the XML messages in the order they are sent to the console. This may be useful to inspect the whole protocol "by hand".
@author Henning Staib
-
org.jnetstream.protocol.Protocol
Contains basic information about a protocol such as a unique ID that is only valid in single VM and single instance, name of the protocol. This is the base interface for {@link ProtocolInfo} which provides more information aboutthe protocol and also acts as a {@link ProtocolRegistry} entry.
@author Mark Bednarczyk
@author Sly Technologies, Inc.
-
org.jnode.net.nfs.Protocol
-
org.jredis.protocol.Protocol
Protocol is effectively a {@link Message} factory. Implementations of this interfaceprovides Message objects that read and write according to a specific Redis protocol specification.
Implementations may use this interface to address issues regarding buffer management. [TODO: document me!]
@author Joubin Houshyar (alphazero@sensesay.net)
@version alpha.0, 04/02/09
@since alpha.0
-
org.mcisb.massspectrometry.pride.model.ExperimentType.Protocol
-
org.menacheri.jetserver.protocols.Protocol
This interface defines a protocol that needs to be applied while communicating to the user session object. For the netty implementation, this would mean that the protocol would be a series of handlers, decoders and encoders added to the pipeline associated with this session to enable the relevant protocol. For Example, the STRING protocol would add string encoder and decoder to the pipeline. AMF3 would add the relevant serializer and de-serializer to the pipeline.
@author Abraham Menacherry
-
org.omg.RTCORBA.Protocol
Generated from IDL struct "Protocol".
@author JacORB IDL compiler V 2.3.2 (JBoss patch 0), 23-Dec-2011
@version generated at Apr 17, 2012 2:17:17 PM
-
org.platformlayer.ops.firewall.Protocol
-
org.qi4j.test.indexing.model.Protocol
JAVADOC Add JavaDoc.
-
org.restlet.client.data.Protocol
Protocol used by client and server connectors. Connectors enable the communication between components by implementing standard protocols.
@author Jerome Louvel
-
org.restlet.data.Protocol
Protocol used by client and server connectors. Connectors enable the communication between components by implementing standard protocols.
@author Jerome Louvel
-
org.salamandra.web.core.transformer.node.tx.TrXFactory.Protocol
-
quicktime.app.spaces.Protocol
@deprecated