Enhanced Session Storage Access
You can store information in the storage of various session types, such as Client/Server, Web, or Mobile, allowing for easy reuse across different processes.
Now, in 4D 20 R6, you can access the storage of a specific session. This enhancement enables users to easily maintain the continuity and consistency of information across multiple sessions of the same user. Imagine being able to pull up the same customer record across different applications such as Client/Server or Web.
Managing HTTP Requests with HTTP Agents
In 4D 19 R6, we introduced HTTP classes to modernize syntax and enhance functionalities for our HTTP client commands. Building on this foundation, 4D 20 R6 brings a powerful new feature: HTTP agents. These agents empower developers to customize and optimize their connections to HTTP servers by managing connection persistence and reuse for HTTP requests.
Easily Using Qodly’s REST API
A few months ago, we announced that Qodly Studio is now available to all our Silver Partners (and higher).
Qodly Studio for 4D is fully integrated into 4D, allowing 4D Server to host your application with both desktop and web pages.
Qodly Studio is also accessible on Qodly, as part of 4D’s newly launched SaaS offering. This innovative hybrid low-code solution is specifically designed for web browser-based business applications.
Even if you’ve already built apps using the Qodly platform, we have more good news! You can now with 4D 20 R5 utilize the REST API of a Qodly application to seamlessly work with your data.
Keep reading to learn more.
When Qodly.com Meets 4D Server, What Are They Talking About?
Last September, 4D unveiled Qodly Studio for 4D, offering comprehensive benefits that enable you to seamlessly create dynamic, efficient business web applications. If you haven’t yet, check out this blog post to learn how to get started with Qodly Studio for 4D.
Qodly Studio is also accessible on qodly.com, forming a part of 4D’s new SaaS offering.
Excitingly, the synergy between Qodly.com and 4D applications reaches new heights with the introduction of the QodlyScript openDatastore command. This feature enables qodly.com web applications to seamlessly connect with 4D applications deployed on 4D Servers, facilitating the utilization of 4D projects as remote datastores. So, if you’re eager to harness the power of your 4D application data and business logic within a qodly.com environment, you’ll be delighted to learn about the possibilities offered by Qodly Studio’s latest advancements.
Now, picture this scenario: your existing 4D Server-based application serves both desktop and web clients using Qodly forms. If this setup mirrors your current approach, feel free to skip ahead.
But if you want to extend your existing 4D server-based application with a totally new one, only web-based – and this one hosted on Qodly.com then this post is for you and shows how to communicate between both.
Simplifying Component Management in 4D
In the context of 4D development, managing components typically involves a substantial amount of work. However, introducing the Component Manager feature in the 4D environment represents a significant advancement in component management.
No longer confined to placing components in a designated Components folder, this feature relies on two key elements: dependencies.json and environment4d.json. Since 4D 20 R5, these files offer developers better visibility into application dependencies and the flexibility to customize component paths.
Explore GitHub Codespaces Possibilities with 4D
GitHub offers powerful tools for developers. One of them is Codepaces, which lets you develop code stored in a GitHub repo online from anywhere using an integrated instance of Visual Studio Code.
This is also the case with 4D projects!
Let’s discover this powerful tool and see a new way of coding!
Auto Tool4D Download in 4D-Analyzer Extension for VS Code
We’re pleased to announce a useful new simplification in the 4D-Analyzer extension for Visual Studio Code!
This feature is aimed at streamlining the process of getting started and enhancing development with VS Code for 4D.
Until now, the 4D-Analyzer extension for VS Code required a 4D application (4D, 4D Server, or tool4d) running in the background. This setup enabled the extension to communicate with the 4D LSP (Language Server Protocol) server.
However, this requirement has been eliminated with the release of version 0.2.0 of the extension.
Deprecation of the Legacy Network Layer
To handle the communication between 4D Client and 4D Server, 4D proposes 3 different network layers:
- Legacy,
- ServerNet,
- and QUIC.
The Legacy network layer was introduced 30 years ago in 4D v3. It was originally developed for AppleTalk, enhanced for ISDN, and then added IPX and finally TCP/IP.
It was created for a very different Client/Server usage than 4D works today: it is single-threaded, optimized for slow networks with no encryption, and available for many different network protocols. As such, it is not optimized at all for modern network communications and supports a very limited number of features.
That’s why, with 4D 20 R5, we have decided to make the Legacy network layer obsolete and plan to remove it soon. We encourage you to move to ServerNet now if you are still using it. Let me explain what benefits you will get from the switch.
4D Netkit: OAuth2.0 authentication using a certificate
Several OAuth 2.0 servers, like the Microsoft Identity Platform, provide an authentication option utilizing certificates instead of client secrets. This approach enhances security and authentication mechanisms within the protocol. Starting from version 4D 20 R5, Netkit incorporates OAuth 2.0 certificate-based connection management.
Contact us
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy