Re: [Cppcms-users] Next CppCMS Feature Poll

[Nazim C. B. <nz...@pr...>]

Hello,

I would like to cast my vote for 4th item: clean-up the code for C++11, implement (and use) move semantics.

In my opinion, today's web app. stacks are not monolithic/uniform. But instead, collaborative pieces running together and not always but mostly there is a web server (like nginx) greeting visitors. HTTP/1.1, HTTP/2 and SSL already available and it shouldn't be the most priority item (of course it could be nice to have them).

And I would like to propose here that, if you need help I can provide 3 hours per workday (15 hours per week) of development support. You can create milestone on GitHub, and split work as issues, and whoever would like to help may request to be assignee of any issue, write the code and create pull request. Well, please thing about it ;)

Kind regards,
Nazim Can.

-------- Original Message --------
On 10 Aug 2020, 22:01, Artyom Beilis wrote:

> Hello All,
>
> Following the discussion I want to make a commitment to implement a
> new feature required by the community. Here my options:
>
> 1. HTTP/1.1 support - it would allow keep alive support and better
> performance overall for multiple requests. It would allow future
> implementation of web sockets.
> 2. Multiple-Event-Loop support - today there is only 1 event loop for
> the service and it can be a bottleneck for small requests on systems
> with high core count
> 3. SSL support - for embedded systems that need proper web server
> 4. C++11 cleanup - replace all booster primitives that exist in C++11
> with standard (shared_ptr, thread, mutex, etc) provide move
> constructors for many objects, replace auto_ptr by unique_ptr.
>
> Feel free to suggest other ideas that you can think of that would be beneficial
>
> Artyom Beilis
>
> _______________________________________________
> Cppcms-users mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppcms-users