 9bdcbe0447
			
		
	
	9bdcbe0447
	
	
	
		
			
			Major integrations and fixes: - Added BACKBEAT SDK integration for P2P operation timing - Implemented beat-aware status tracking for distributed operations - Added Docker secrets support for secure license management - Resolved KACHING license validation via HTTPS/TLS - Updated docker-compose configuration for clean stack deployment - Disabled rollback policies to prevent deployment failures - Added license credential storage (CHORUS-DEV-MULTI-001) Technical improvements: - BACKBEAT P2P operation tracking with phase management - Enhanced configuration system with file-based secrets - Improved error handling for license validation - Clean separation of KACHING and CHORUS deployment stacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
		
			
				
	
	
		
			28 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
			
		
		
	
	
			28 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
| // The pubsub package provides facilities for the Publish/Subscribe pattern of message
 | |
| // propagation, also known as overlay multicast.
 | |
| // The implementation provides topic-based pubsub, with pluggable routing algorithms.
 | |
| //
 | |
| // The main interface to the library is the PubSub object.
 | |
| // You can construct this object with the following constructors:
 | |
| //
 | |
| // - NewFloodSub creates an instance that uses the floodsub routing algorithm.
 | |
| //
 | |
| // - NewGossipSub creates an instance that uses the gossipsub routing algorithm.
 | |
| //
 | |
| // - NewRandomSub creates an instance that uses the randomsub routing algorithm.
 | |
| //
 | |
| // In addition, there is a generic constructor that creates a pubsub instance with
 | |
| // a custom PubSubRouter interface. This procedure is currently reserved for internal
 | |
| // use within the package.
 | |
| //
 | |
| // Once you have constructed a PubSub instance, you need to establish some connections
 | |
| // to your peers; the implementation relies on ambient peer discovery, leaving bootstrap
 | |
| // and active peer discovery up to the client.
 | |
| //
 | |
| // To publish a message to some topic, use Publish; you don't need to be subscribed
 | |
| // to the topic in order to publish.
 | |
| //
 | |
| // To subscribe to a topic, use Subscribe; this will give you a subscription interface
 | |
| // from which new messages can be pumped.
 | |
| package pubsub
 |