You are not logged in.
Pages: 1
Supporting Delphi for Linux support is fantastic! ![]()
Can you explain a little bit more?
Sure.
When I use THttpApiServer, I can add multiple routes with different ports using AddUrl.
For example:
AddUrl('test1','8056')
AddUrl('test2','8097')
But when I am using THTTPServer, it seems I can only pass the port parameter to the constructor, it does not support to bind different routes to different ports.
I'm using THttpApiServer to achieve this goal in the past, which works great.
But now I'm tring to port the application to Linux, so THttpApiServer is no longer an option.
Do I have to create multiple THttpServer instance to achieve the same goal?
It seems the first step is done:
https://github.com/synopse/mORMot2/comm … 2d45a29e61
I think the whole community will welcome this change!
So did I. Most of the code just work after changing platforms, except for the parts relying on Windows unit. For us, performance is already good enough; compatibility is our main concern.
Will Delphi for Linux support still be considered in the roadmap?
Surely we could use FPC for new projects. But a lot of people like me are trying to migrate the old Windows project to Linux, a total rewrite in FPC is often not practical. To be honst, I have used a lot of 3rd party libraries in my project, but for now mORMot is the last 3rd party library that does not support Delphi for Linux. I have to write a adapter to use mORMot and Indy version of HTTP Server.
Any plans to support WebTransport Server?
https://developer.mozilla.org/en-US/doc … bTransport
Do we have any progress on this? I see some related commits, but the issue we discussed is not fixed.
But switching cores might not be an instant behavior.
That's great!
My thought is always, correctness first, performance later.
This could also happen when only one or some cores are 100% usage, not all cores.
The Github issue was closed. But I still think there are some race conditions.
Pages: 1