Since the introduction of scalable sessions, server-side session management has become an important component of modern 4D architectures. These sessions enable fine-tuned scalability for web applications, but also require stricter supervision to guarantee performance, stability, and license control. With 4D 21, you now have a comprehensive means of inspecting all open web sessions, whether they originate from REST connections, SOAP calls, or 4DACTION requests.
The Process activity command has been enhanced to faithfully reflect server-side network activity. It now provides a list of all active sessions, including:
- Sessions created by SOAP services,
- REST sessions opened via 4DACTION.
Process activity(Session only)
This gives administrators and developers full transparency into how the server is being used at any given time.
In addition, during the authentication process, if you choose to explicitly name the user via the “Session.setPrivilege()” function, you can easily identify the connected user.
Session.setPrivilege({userName: "name"})
This simple step makes it much easier to identify connected users. It also facilitates information sharing between sessions, since you can access any session storage by its unique ID. This is especially useful for sharing data between processes. The data saved in the session storage can also be used to dynamically filter the results returned by the “Restrict” event, allowing you to restrict data access based on the session context.
Example:
[
{
"creationDateTime": "2025-08-07T14:26:10Z",
"hostType": "browser",
"ID": "07FEE39015C447B0B67D2220E528D563",
"IPAddress": "localhost",
"machineName": "",
"state": "active",
"type": "rest",
"userName": "John Doe"
}
]
In summary
This new information, accessible via the Process activity command, makes it considerably easier to monitor, audit, and optimize connections. You’ll gain greater visibility into the actual use of your server, enabling you to make better decisions on a day-to-day basis.