mleku
b1f1334e39
- Introduced a new `ClusterManager` to handle cluster membership events and facilitate event replication across relay peers. - Implemented HTTP endpoints for retrieving the latest serial and fetching events within a specified range. - Enhanced event handling to process cluster membership events (Kind 39108) and update relay lists accordingly. - Updated configuration to support cluster administrators and their management capabilities. - Added comprehensive tests to validate the new cluster replication functionalities. - Documented the cluster replication protocol in a new specification file. - Bumped version to reflect these changes.
17 lines
988 B
Markdown
17 lines
988 B
Markdown
# DEPRECATED: This NIP has been replaced
|
|
|
|
**This document has been superseded by [NIP-XX-Cluster-Replication.md](NIP-XX-Cluster-Replication.md)**
|
|
|
|
The distributed directory consensus protocol described in this document has been replaced by the HTTP-based pull replication protocol defined in the Cluster Replication NIP. The new protocol provides more efficient traffic patterns through active polling rather than push-based event replication.
|
|
|
|
## Migration
|
|
|
|
If you were implementing or using the protocol described in this document:
|
|
|
|
1. **Stop using** the WebSocket event-based replication (Kinds 39100-39112)
|
|
2. **Switch to** the HTTP polling-based cluster replication protocol
|
|
3. **Update membership management** to use Kind 39108 events published by cluster administrators
|
|
4. **Configure polling** to use the `/cluster/latest` and `/cluster/events` HTTP endpoints
|
|
|
|
See [NIP-XX-Cluster-Replication.md](NIP-XX-Cluster-Replication.md) for the complete specification of the new protocol.
|