integrate the bi-direction comm into one func, but may lead to unexpected dead lock.

NewBlock creates a new Block given the input parameters.

NewBlock creates a new Block given the input parameters.

NewChaincodeDeployTransaction is used to deploy chaincode.

NewChaincodeExecute is used to invoke chaincode.

A transaction which is applied on a EXISTED single chaincode (i.e.: invoke or query ...) (it is not easy to handle deployment in the same entry) This is used to replace the deprecated NewTransaction entry input chaincode is handled and wrapped into generated chaincodespec field.

NewBlock creates a new Block given the input parameters.

YA-fabric 0.9: deprecated this NewTransaction creates a new transaction.

create a new transaction with its "core" field is specified.

parse the chaincode name in YA-fabric 0.9's standard form: [templateName:]ccName[@LedgerName].

UnmarshallBlock converts a byte array generated by Bytes() back to a block.

new register, using a extended struct instead of chaincodeID.

client using this message for acking a message fromserver's current session, it may piggyback next requestin this message sever should always handle the newest requestand drop the task it received beforethe fields of session and ack may both existclient MUST prepare for receiving unexpected data package from previousrequest because they may have been in wired before new requestis delivered.

when request, its correlationId incidate the id ofsession, which must be unique to any other simple requestor sessions it has requested for (no matter accepted or not).

err can be sent at any time, the correlationId incidateits corresponding request or session.

deploy a chaincode to the network and call `Init` function.

call a chaincode `Invoke` function as a transaction.

call a chaincode `query` function.

terminate a chaincode; not implemented yet.

default handler provided a base routine for picking a tx into execution enviroment again(e.g.

allowing interrupt among a prehandler array and set the whold result as correct.

name handler should be the very first one before any working handling (Except simple tagging)start, so handling specfied by ccname can work.

reponse for the opensession message, more detail may be providedso client can prepare a better plan in transferring.

Block carries The data that describes a block in the blockchain.

Contains information about the blockchain ledger such as height, current block hash, and previous block hash.

Specifies the current number of blocks in the blockchain.

Specifies the block number to be returned from the blockchain.

Specify the deployment of a chaincode.

ChaincodeEvent is used for events and registrations that are specific to chaincodestring type - "chaincode".

ChaincodeID contains the path as specified by the deploy transactionthat created it as well as the hashCode that is generated by thesystem for the path.

Carries the chaincode function and its arguments.

Carries the chaincode function and its arguments.

ChaincodeReg is used for registering chaincode Interestswhen EventType is CHAINCODE.

This structure contain transaction data that we send to the chaincode container shim and allow the chaincode to access through the shim interface.

Carries the chaincode specification.

Event is used by - consumers (adapters) to send Register - producer to advertise supported types and events.

Globalstate defines the global graph of all states.

TransactionBlock carries a batch of transactions.

simple state sync via msg-pushing.

NonHashData is data that is recorded on the block, but not included in the block hash when verifying the blockchain.

request to open a long hold transferringclient must specified a "open for" fieldso server can prepare for the following transfermationprocess, or simply reject it.

extended peerid for connection in separated streams, company withthe one-time password.

---------- consumer events ---------Register is sent by consumers for registering eventsstring type - "register".

Rejection is sent by consumers for erroneous transaction rejection eventsstring type - "rejection".

can be sent by server during any time of a session.

Secret is a temporary object to establish security with the Devops.

simple syncing req/resp, the resp should have the same correlationId withthe incoming.

a simple bloom filter information for representing a group of state the filter is expressed by a bytes string less than 8k (65535bit) and has 8*<bytes> buckets a target hash is separated into WORDs (16bit) and the first n (n=hashCounts) WORD is used in the filter if the length of target has no enough WORDs, the hashes of rest are considered as 0.

StateIndex is the payload in response to the index/query request (but the response in query may not contain corePayload field).

a default implement, use two goroutine for read and write simultaneously.

SyncStateDeltas is the payload in response to the block request message.

SyncBlockRange is the payload of block request, where start and end indicate the starting and ending blocks inclusively.

Like chat, stateSync wrap messages used in a syncing session.

we have one of the following fields specified by the typebytes payload = 3;.

we have specified field for each implement of states (buckettree, trie, etc.).

SyncStateChunk is the payload to the request of state syncing request.

SyncStateDeltas is the payload in response to the delta request message.

Transaction defines a function call to a contract.

TransactionBlock carries a batch of transactions.

YA-fabric 0.9： We define a struct for transaction which is passed in a pipeline handling it, the data can be completed progressively along the pipeline and finally be delivered for executing.

TransactionResult contains the return value of a transaction.

request wrap one of the request field which has been negotiated inhandshake phase.

the response contain one of the payload and client should knowwhich field it should check, its seq field is which transferAck can ack for,(notice seq is 32bit so there will be an implicit constration that ano more than 4G messages can be transferred in one session)it must be unique for each response messageand incremental during a whole session.

query some transactions, and the response should be a TransactionBlock message.

---------- producer events ---------.

AdminClient is the client API for Admin service.

AdminServer is the server API for Admin service.

ChaincodeSupportClient is the client API for ChaincodeSupport service.

ChaincodeSupportServer is the server API for ChaincodeSupport service.

DevopsClient is the client API for Devops service.

DevopsServer is the server API for Devops service.

EventsClient is the client API for Events service.

EventsServer is the server API for Events service.

GossipClient is the client API for Gossip service.

GossipServer is the server API for Gossip service.

OpenchainClient is the client API for Openchain service.

OpenchainServer is the server API for Openchain service.

PeerClient is the client API for Peer service.

PeerServer is the server API for Peer service.

a streamhandler factory include two methods: 1.

each streamhandler implement exposed following methods for working in a streaming, it supposed message with certain type is transmitted in the stream and each end handle this message by a streamhandler implement: Tag: providing a string tag for the implement EnableLoss: indicate the message transmitted in stream can be dropped for any reason (send buffer full, bad linking, deliberately omitted by the other side ...) NewMessage: provided a prototype object of the transamitted message for receiving and handling later in a HandleMessage call HandleMessage: handling a message received from the other side.

SyncClient is the client API for Sync service.

SyncServer is the server API for Sync service.

Confidentiality Levels.

convert a function to a prehandler interface.

a function filter the pure tx can also be converted to a prehandler interface.