docs: 📖 Clarify WebSockets extension page purpose

versia-pub · Sep 9, 2024 · c17852a · c17852a
1 parent ec9cb1e
commit c17852a
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/app/extensions/websockets/page.mdx b/app/extensions/websockets/page.mdx
@@ -7,9 +7,9 @@ export const metadata = {
 # WebSockets Extension
 
 <Note>
-    This extension is a **draft** and should not be considered final. It is subject to change.
+    This document is **provided for informative purposes** and should not be used in a production environment. It is subject to change.
 
-    If testing proves unsuccessful, this draft may be abandoned.
+    If internal testing proves unsuccessful at solving the problems with the HTTP delivery method, this document may be abandoned.
 </Note>
 
 Typically, communication between Versia instances is done via HTTP. However, HTTP suffers from some limitations, such as high latency and heavy overhead for small messages, making it less suitable for exchanging large amounts of entities at acceptable speeds. {{ className: 'lead' }}