system

Documentation

Index

• Constants
• func NewCSCCV1(peerPool api.PeerPool, identity msp.SigningIdentity) api.CSCC
• func NewCSCCV2(peerPool api.PeerPool, identity msp.SigningIdentity) api.CSCC
• func NewLSCC(peerPool api.PeerPool, identity msp.SigningIdentity) api.LSCC
• func NewLifecycle(core api.Core) *lifecycleCoreFacade
• func NewQSCC(peerPool api.PeerPool, identity msp.SigningIdentity) api.QSCC
• func NewSCC(core api.Core) api.SystemCC

Constants

const (
	JoinChain      string = "JoinChain"
	GetConfigBlock string = "GetConfigBlock"
	GetChannels    string = "GetChannels"
	GetConfigTree  string = `GetConfigTree`
)

These are function names from Invoke first parameter

const (
	GetChannelConfig string = "GetChannelConfig"
)

These are function names from Invoke first parameter

Functions

func NewCSCCV1

func NewCSCCV1(peerPool api.PeerPool, identity msp.SigningIdentity) api.CSCC

func NewCSCCV2

func NewCSCCV2(peerPool api.PeerPool, identity msp.SigningIdentity) api.CSCC

func NewLSCC

func NewLSCC(peerPool api.PeerPool, identity msp.SigningIdentity) api.LSCC

func NewLifecycle

func NewLifecycle(core api.Core) *lifecycleCoreFacade

NewLifecycle About separation of implementations Thing is: new fabric v2 lifecycle uses discovery for some methods, and for some doesn't we don't want to use discovery everytime because some services must work just with one home-peer and shouldn't(and doesn't want to) know about rest topogy/configuration

func NewQSCC

func NewQSCC(peerPool api.PeerPool, identity msp.SigningIdentity) api.QSCC

func NewSCC

func NewSCC(core api.Core) api.SystemCC