4d · arnaud4d · Apr 20, 2026 · Apr 13, 2026 · Apr 13, 2026 · Apr 13, 2026
diff --git a/docs/API/BlobClass.md b/docs/API/BlobClass.md
@@ -5,6 +5,12 @@ title: Blob
 
 The Blob class lets you create and manipulate [blob objects](../Concepts/dt_blob.md#blob-types) (`4D.Blob`).
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
 ### Summary
 
 ||

diff --git a/docs/API/CollectionClass.md b/docs/API/CollectionClass.md
@@ -9,6 +9,11 @@ The Collection class manages [Collection](Concepts/dt_collection.md) type expres
 A collection is initialized with the [`New collection`](../commands/new-collection) or [`New shared collection`](../commands/new-shared-collection) commands.
 
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
 
 ### Example
 
@@ -3290,7 +3295,7 @@ By default, new elements are filled will **null** values. You can specify the va
 
 </details>
 
-<!-- REF #collection.reverse().Syntax -->**.reverse( )** : Collection <!-- END REF -->
+<!-- REF #collection.reverse().Syntax -->**.reverse()** : Collection <!-- END REF -->
 
 
 <!-- REF #collection.reverse().Params -->
@@ -3305,7 +3310,7 @@ By default, new elements are filled will **null** values. You can specify the va
 
 #### Description
 
-The `.reverse()` function <!-- REF #collection.reverse().Summary -->returns a deep copy of the collection with all its elements in reverse order<!-- END REF -->. If the original collection is a shared collection, the returned collection is also a shared collection.
+The `.reverse()` function <!-- REF #collection.reverse().Summary -->returns a new collection with all elements of the original collection in reverse order<!-- END REF -->. If the original collection is a shared collection, the returned collection is also a shared collection.
 
 >This function does not modify the original collection.
 

diff --git a/docs/API/EmailObjectClass.md b/docs/API/EmailObjectClass.md
@@ -16,6 +16,13 @@ You send `Email` objects using the SMTP [`.send()`](SMTPTransporterClass.md#send
 
 [`MAIL Convert from MIME`](../commands/mail-convert-from-mime) and [`MAIL Convert to MIME`](../commands/mail-convert-to-mime) commands can be used to convert `Email` objects to and from MIME contents.
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
+
 ### Email Object
 
 Email objects provide the following properties:

diff --git a/docs/API/FileClass.md b/docs/API/FileClass.md
@@ -5,6 +5,14 @@ title: File
 
 `File` objects are created with the [`File`](../commands/file) command. They contain references to disk files that may or may not actually exist on disk. For example, when you execute the `File` command to create a new file, a valid `File` object is created but nothing is actually stored on disk until you call the [`file.create( )`](#create) function.
 
+
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
+
 ### Example
 
 The following example creates a preferences file in the project folder:

diff --git a/docs/API/FileHandleClass.md b/docs/API/FileHandleClass.md
@@ -17,7 +17,6 @@ Object resources, such as documents, are released when no more references exist
 
 :::
 
-
 ### Example
 
 ```code4d
@@ -57,6 +56,7 @@ End while
 
 ```
 
+
 ### FileHandle object
 
 File handle objects cannot be shared.

diff --git a/docs/API/FolderClass.md b/docs/API/FolderClass.md
@@ -7,6 +7,14 @@ title: Folder
 
 `Folder` objects are created with the [`Folder`](../commands/folder) command. They contain references to folders that may or may not actually exist on disk. For example, when you execute the `Folder` command to create a new folder, a valid `Folder` object is created but nothing is actually stored on disk until you call the [`folder.create()`](#create) function.
 
+
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
+
 ### Example
 
 The following example creates a "JohnSmith" folder:

diff --git a/docs/API/FormulaClass.md b/docs/API/FormulaClass.md
@@ -13,6 +13,12 @@ title: Formula
 
 See examples in the [Executing code in Function objects](../API/FunctionClass.md#executing-code-in-function-objects) paragraph.
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
 
 ### Passing parameters to formulas
 

diff --git a/docs/API/IMAPNotifierClass.md b/docs/API/IMAPNotifierClass.md
@@ -0,0 +1,160 @@
+---
+id: IMAPNotifierClass
+title: IMAPNotifier
+---
+
+The `IMAPNotifier` class allows you to manage IMAP IDLE notifications for a selected mailbox.
+
+<details><summary>History</summary>
+
+|Release|Changes|
+|---|---|
+|21 R3|Class added|
+
+</details>
+
+The `IMAPNotifier` class is available from the `4D` class store.
+
+An `IMAPNotifier` object is associated with an [IMAP transporter](./IMAPTransporterClass.md#imap-transporter-object) and provides access to mailbox notification management.
+
+All `IMAPNotifier` class functions are thread-safe.
+
+:::tip Related Blog post
+
+[Instant Email Notifications with IMAP Transporter](https://blog.4d.com/instant-email-notifications-with-imap-transporter)
+
+:::
+
+### Example
+
+```4d
+// Define listener callbacks
+var $parameter : Object
+var $transporter : 4D.IMAPTransporter
+
+$parameter:=New object
+$parameter.authenticationMode:=IMAP authentication OAUTH2
+$parameter.host:="Outlook.office365.com"
+$parameter.port:=993
+$parameter.accessTokenOAuth2:=$myToken
+$parameter.user:="myaddress@email.com"
+$parameter.listener:=cs.IMAPListener.new()
+
+$transporter:=IMAP New transporter($parameter)
+$transporter.selectBox("INBOX")
+
+$transporter.notifier.start()     
+```     
+
+## IMAPNotifier object
+
+An IMAPNotifier object provides the following properties and functions:   
+
+||
+|---|
+| [<!-- INCLUDE #IMAPNotifier.isStarted.Syntax -->](#isstarted)<br/><!-- INCLUDE #IMAPNotifier.isStarted.Summary --> |
+| [<!-- INCLUDE #IMAPNotifier.start().Syntax -->](#start)<br/><!-- INCLUDE #IMAPNotifier.start().Summary -->         |
+| [<!-- INCLUDE #IMAPNotifier.stop().Syntax -->](#stop)<br/><!-- INCLUDE #IMAPNotifier.stop().Summary -->            |
+
+
+<!-- REF 4D.IMAPNotifier.new().Desc -->
+## 4D.IMAPNotifier.new()
+
+<!-- REF #4D.IMAPNotifier.new().Syntax -->**4D.IMAPNotifier.new**() : 4D.IMAPNotifier<!-- END REF -->
+
+<!-- REF #4D.IMAPNotifier.new().params -->
+|Parameter|Type||Description|
+|---|---|---|---|
+|Result|4D.IMAPNotifier|<-|New IMAPNotifier object|
+<!-- END REF -->
+
+#### Description
+
+The `4D.IMAPNotifier.new()` function <!-- REF #4D.IMAPNotifier.new().Summary -->creates a new IMAPNotifier object<!-- END REF -->.
+
+<!-- END REF -->
+
+<!-- REF IMAPNotifier.isStarted.Desc -->
+## .isStarted
+
+<!-- REF #IMAPNotifier.isStarted.Syntax -->**.isStarted** : Boolean<!-- END REF -->
+
+#### Description
+
+The `.isStarted` property <!-- REF #IMAPNotifier.isStarted.Summary -->indicates whether the notifier is started (`true`) or stopped (`false`)<!-- END REF -->. This property is **read-only**.
+
+<!-- END REF -->
+
+
+<!-- REF IMAPNotifier.start().Desc -->
+## .start()
+
+<!-- REF #IMAPNotifier.start().Syntax -->**.start**() : Object<!-- END REF -->
+
+<!-- REF #IMAPNotifier.start().params -->
+|Parameter|Type||Description|
+|---------|--- |:---:|------|
+|Result|Object|<-|Operation status|
+<!-- END REF -->
+
+#### Description
+
+The `.start()` function <!-- REF #IMAPNotifier.start().Summary -->starts the subscription to server notifications and activates IMAP listener callbacks<!-- END REF -->.
+
+A mailbox must be selected using [`selectBox()`](./IMAPTransporterClass.md#selectbox) before calling `.start()`.
+
+Callback functions are executed in the worker where `.start()` is called.  
+
+:::note Notes
+
+* When the notifier is started, other transporter functions (such as `getMail()` or `send()`) are not available. You must call `.stop()` before using these functions, then call `.start()` again to resume notifications.
+
+* IMAP IDLE notifications indicate that a change has occurred but do not provide updated mailbox data. To refresh the mailbox state, you must stop the notifier, retrieve the updated data (for example using `getMail()`), and then restart it.
+
+:::
+
+#### Returned object
+
+|Property||Type|Description|
+|---|---|---|---|
+|success||Boolean|True if the operation is successful, False otherwise|
+|statusText||Text|Status message returned by the IMAP server, or last error returned in the 4D error stack|
+|errors||Collection|4D error stack (not returned if a server response is received)|
+||\[].errcode|Number|4D error code|
+||\[].message|Text|Description of the error|
+||\[].componentSignature|Text|Signature of the component that returned the error|
+
+<!-- END REF -->
+
+
+<!-- REF IMAPNotifier.stop().Desc -->
+## .stop()
+
+<!-- REF #IMAPNotifier.stop().Syntax -->**.stop**() : Object<!-- END REF -->
+
+<!-- REF #IMAPNotifier.stop().params -->
+|Parameter|Type||Description|
+|---------|--- |:---:|------|
+|Result|Object|<-|Operation status|
+<!-- END REF -->
+
+#### Description
+
+The `.stop()` function <!-- REF #IMAPNotifier.stop().Summary -->stops the notification subscription<!-- END REF -->. Calling `.stop()` is required before using other transporter functions (such as `getMail()` or `send()`).
+
+#### Returned object
+
+|Property||Type|Description|
+|---|---|---|---|
+|success||Boolean|True if the operation is successful, False otherwise|
+|statusText||Text|Status message returned by the IMAP server, or last error returned in the 4D error stack|
+|errors||Collection|4D error stack (not returned if a server response is received)|
+||\[].errcode|Number|4D error code|
+||\[].message|Text|Description of the error|
+||\[].componentSignature|Text|Signature of the component that returned the error|
+
+<!-- END REF -->
+
+
+
+
diff --git a/docs/API/IMAPTransporterClass.md b/docs/API/IMAPTransporterClass.md
@@ -31,7 +31,8 @@ IMAP Transporter objects are instantiated with the [IMAP New transporter](../com
 |[<!-- INCLUDE #IMAPTransporterClass.getMIMEAsBlob().Syntax -->](#getmimeasblob)<br/><!-- INCLUDE #IMAPTransporterClass.getMIMEAsBlob().Summary -->|
 |[<!-- INCLUDE #transporter.host.Syntax -->](#host)<br/><!-- INCLUDE #transporter.host.Summary -->|
 |[<!-- INCLUDE #transporter.logFile.Syntax -->](#logfile)<br/><!-- INCLUDE #transporter.logFile.Summary -->|
-|[<!-- INCLUDE #IMAPTransporterClass.move().Syntax -->](#move)<br/><!-- INCLUDE #IMAPTransporterClass.move().Summary -->|
+|[<!-- INCLUDE #IMAPTransporterClass.move().Syntax -->](#move)<br/><!-- INCLUDE #IMAPTransporterClass.move().Summary -->|  
+|[<!-- INCLUDE #IMAPTransporterClass.notifier.Syntax -->](#notifier)<br/><!-- INCLUDE #IMAPTransporterClass.notifier.Summary -->|
 |[<!-- INCLUDE #IMAPTransporterClass.numToID().Syntax -->](#numtoid)<br/><!-- INCLUDE #IMAPTransporterClass.numToID().Summary -->|
 |[<!-- INCLUDE #IMAPTransporterClass.removeFlags().Syntax -->](#removeflags)<br/><!-- INCLUDE #IMAPTransporterClass.removeFlags().Summary -->|
 |[<!-- INCLUDE #IMAPTransporterClass.renameBox().Syntax -->](#renamebox)<br/><!-- INCLUDE #IMAPTransporterClass.renameBox().Summary -->|
@@ -53,7 +54,7 @@ IMAP Transporter objects are instantiated with the [IMAP New transporter](../com
 
 |Parameter|Type||Description|
 |---------|--- |:---:|------|
-|server|Object|->|Mail server information|
+|parameter|Object|->|Mail server configuration|
 |Result|4D.IMAPTransporter|<-|[IMAP transporter object](#imap-transporter-object)|
 </div>
 <!-- END REF -->
@@ -1158,6 +1159,7 @@ The optional *updateSeen* parameter allows you to specify if the message is mark
 <!-- INCLUDE transporter.logFile.Desc -->
 
 <!-- REF IMAPTransporterClass.move().Desc -->
+
 ## .move()
 
 <details><summary>History</summary>
@@ -1259,6 +1261,19 @@ To move all messages in the current mailbox:
  $status:=$transporter.move(IMAP all;"documents")
 ```
 
+<!-- END REF -->
+
+  <!-- REF IMAPTransporterClass.notifier.Desc -->
+## .notifier
+
+<!-- REF #IMAPTransporterClass.notifier.Syntax -->**.notifier** : 4D.IMAPNotifier<!-- END REF -->
+
+#### Description
+
+The `.notifier` property <!-- REF #IMAPTransporterClass.notifier.Summary -->contains the IMAPNotifier object associated with the transporter<!-- END REF -->. This property is **read-only**.
+
+See [IMAPNotifier](./IMAPNotifierClass.md).
+
 <!-- END REF -->
 
 <!-- REF IMAPTransporterClass.numToID().Desc -->

diff --git a/docs/API/MailAttachmentClass.md b/docs/API/MailAttachmentClass.md
@@ -5,6 +5,12 @@ title: MailAttachment
 
 Attachment objects allow referencing files within a [`Email`](EmailObjectClass.md) object. Attachment objects are created using the [`MAIL New attachment`](../commands/mail-new-attachment) command.
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
 
 ### Attachment Object
 

diff --git a/docs/API/MethodClass.md b/docs/API/MethodClass.md
@@ -21,6 +21,12 @@ See examples in the [Executing code in Function objects](../API/FunctionClass.md
 
 :::
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+
+:::
+
 
 ### Examples
 

diff --git a/docs/API/SessionClass.md b/docs/API/SessionClass.md
@@ -12,7 +12,7 @@ Session objects are returned by the [`Session`](../commands/session) command. Th
 - [Scalable sessions for advanced web applications](https://blog.4d.com/scalable-sessions-for-advanced-web-applications/)
 - [Permissions: Inspect Session Privileges for Easy Debugging](https://blog.4d.com/permissions-inspect-session-privileges-for-easy-debugging/)
 - [Generate, share and use web sessions One-Time Passcodes (OTP)](https://blog.4d.com/connect-your-web-apps-to-third-party-systems/)
-- [Client / server – Handle a session when working on a 4D client](https://blog.4d.com/client-server-handle-a-session-when-working-on-a-4d-client)
+- [Forget server-side wrappers, use 4D Sessions from the client](https://blog.4d.com/forget-server-side-wrappers-use-4d-sessions-from-the-client)
 
 :::
 

diff --git a/docs/API/VectorClass.md b/docs/API/VectorClass.md
@@ -10,7 +10,11 @@ The `Vector` class allows you to handle **vectors** and to execute distance and
 In the world of AIs, a vector is a sequence of numbers that enables a machine to understand and manipulate complex data. For a detailed overview of the role of vectors with AIs, you can refer to [this page](https://aiforsocialgood.ca/blog/understanding-the-role-of-vectors-in-artificial-intelligence-a-comprehensive-guide).  
 
 
+:::info
+
+This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
 
+:::
 
 ### Understanding the different vector computations 
 

diff --git a/docs/API/WebServerClass.md b/docs/API/WebServerClass.md
@@ -6,14 +6,17 @@ title: WebServer
 
 The `WebServer` class API allows you to start and monitor a web server for the main (host) application as well as each hosted component (see the [Web Server object](WebServer/webServerObject.md) overview). This class is available from the `4D` class store.
 
+### Properties
+
+- **Streamable**: no
+- **Sharable**: no
+
 ### Web Server object
 
 Web server objects are instantiated with the [`WEB Server`](../commands/web-server) command.
 
 They provide the following properties and functions:
 
-### Summary
-
 ||
 |---|
 |[<!-- INCLUDE #WebServerClass.accessKeyDefined.Syntax -->](#accesskeydefined)<br/><!-- INCLUDE #WebServerClass.accessKeyDefined.Summary -->|
-Original file line number
+Diff line change
@@ Expand Up / @@ -5,6 +5,12 @@ title: Blob @@
     The Blob class lets you create and manipulate [blob objects](../Concepts/dt_blob.md#blob-types) (`4D.Blob`).
+    :::info
+    This class is [**streamable**](../Concepts/dt_object.md#binary-streaming-variable-to-blob) in binary.
+    :::
     ### Summary
     ||
@@ Expand Down @@