You are not logged in.
Pages: 1
The HTTP server is one main part of any SOA/REST service, by design.
It is the main entry point of all incoming requests. So it should better be stable and efficient. And should be able to scale in the future, if needed.
There have always been several HTTP servers in mORMot. You can use the HTTP server class you need.
In mORMot 2, we added two new server classes, one for publishing over HTTP, another able to upgrade to WebSockets. The main difference is that they are fully event-driven, so their thread pool is able to scale with thousands of concurrent connections, with a fixed number of threads. It fixes the limitations of previous our socket server.
This is the forum discussion thread for our blog post:
https://blog.synopse.info/?post/2022/05 … n-mORMot-2
Offline
Thank you, Ab, for the dedication and excellence of your framework! This article will help many who are just starting to understand this part of the powerful mORMot!
Offline
Looking forward to testing it out, cheers.
Offline
Wow, congrats! Great addition to the framework.
Offline
Amazing!!!
Many many thanks Arnaud!
Offline
Thanks Arnaud. This is very exciting and must have taken you a lòt of time!
So much appreciated. It is a very useful expansion of the framework.
Can't wait to get my hands on the examples and start playing with this.
Offline
Who share Any examples about this? thx
Offline
For instance https://github.com/synopse/mORMot2/tree … server-raw
And most other samples in the https://github.com/synopse/mORMot2/tree/master/ex folder do have a HTTP server involved.
Offline
Pages: 1