QUIC Now Matches ServerNet Capabilities

The QUIC network layer now supports as many features as the ServerNet network layer. With 4D 20 R5, we added support for IPv6, broadcast, and Single Sign-on on Windows.

Of course, we will continue to improve it in the coming versions to make it the best network layer 4D has ever had.

But for now, let me speak a bit more about the last functionalities we added.

Our primary focus when building the QUIC network layer has always been stability, especially on low-quality networks. The QUIC network layer brilliantly achieves this, with unmatched stability in case of packet loss and improved performance on high-ping networks.

With the generalization of mobile and Wi-Fi networks and their overall reduced stability, it should significantly enhance your customers’ experience.

Still, we don’t write a new network layer without considering the future, so here’s a peek at the latest changes to the QUIC network layer!

Back to the future

What a title to introduce IPv6!

It is true that the transition to IPv6 didn’t go as expected. A decade ago, we were very close to switching the Internet entirely to IPv6, and today… well, we are not there yet. Still, the global transition is closer than it has ever been. The QUIC network layer improves the compatibility of 4D on IPv6 networks compared to ServerNet.

On air

Let me tell you a bit more about the broadcast.

The network options of the Structure Settings show how to publish an application.

When you publish a 4D application, the 4D Server replies to broadcasts from 4D Remotes running on the same subnetwork. Thanks to this feature, you can see your application in the Available tab of the Connection to 4D Server dialog. Similarly, it allows your engined application to connect automatically to its server the first time you run it.

Your application is set to run with the QUIC network layer, which fully supports broadcast. At the same time, 4D broadcasts are now more accurate; you won’t see them because they are running engined applications other than your own. This is also valid for the ServerNet layer!

SSO on windows

Thanks to Single Sign On, 4D is able to authenticate your users automatically through your Active Directory. Just check the “Authentication of user with domain server” box from the network options of the Structure Settings, and when your users connect to the server, you’ll be able to get their credentials by calling:

$login:=Current client authentication($domain; $protocol)

You’ll receive the user login and domain, as well as the protocol used (NTLM or Kerberos), allowing you to authenticate them without resorting to a login/password dialog.

We are waiting for your feedback.

We’re committed to addressing any issues you encounter and value your feedback.

Don’t hesitate to use the QUIC network layer and provide us with feedback on the 4D forum. Thank you for being a part of this!