From 8839b8d97d17ac5dcc00fd98b62160fb78eb8395 Mon Sep 17 00:00:00 2001 From: Timo K Date: Tue, 7 May 2024 18:53:38 +0200 Subject: [PATCH] Add msc number Signed-off-by: Timo K --- ...ents.md => 4140-expiring-events-with-keep-alive-endpoint.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename proposals/{0000-keep-alive-state-events.md => 4140-expiring-events-with-keep-alive-endpoint.md} (98%) diff --git a/proposals/0000-keep-alive-state-events.md b/proposals/4140-expiring-events-with-keep-alive-endpoint.md similarity index 98% rename from proposals/0000-keep-alive-state-events.md rename to proposals/4140-expiring-events-with-keep-alive-endpoint.md index 6eeb05865..b49671a35 100644 --- a/proposals/0000-keep-alive-state-events.md +++ b/proposals/4140-expiring-events-with-keep-alive-endpoint.md @@ -1,4 +1,4 @@ -# MSC0000: Expiring events with keep alive functionality +# MSC4140: Expiring events with keep alive endpoint Currently there is not mechanism for a client to provide a reliable way of communicating that an event is still valid. The best expiration method is to post