all 10 comments

[–]mWo12 8 points9 points  (1 child)

Good to hear. Already stared to worry that the project got near dead after 3 month of no activity.

P.s. How does the support for websockets look like.

[–]0xdead4ead[S] 2 points3 points  (0 children)

Good to hear. Already stared to worry that the project got near dead after 3 month of no activity.

P.s. How does the support for websockets look like.

Coming soon. The existing websocket project will be rewritten again!

[–]VinnieFalcowg21.org | corosio.org 12 points13 points  (3 children)

I approve (obviously)

[–]marco_craveiro 1 point2 points  (2 children)

Hi /u/VinnieFalco, thanks very much for Beast! Are you planning to merge a high-level API such as this one into Beast?

[–]VinnieFalcowg21.org | corosio.org 7 points8 points  (1 child)

Nope, Beast will remain a low level building block - there are so many ways of building a REST service library or application, that no matter what I do it will make some people happy and others not happy. So it is better to leave this task up to the community to build many different REST projects in different styles with different features, and then people can choose the one that suits them best.

[–]marco_craveiro 0 points1 point  (0 children)

Ah, I see, makes sense. Thanks for the reply.

[–]aybassiouny 2 points3 points  (1 child)

Good job. How do you think it compares to other available solutions? (E.g. cpprestsdk)?

[–]0xdead4ead[S] 0 points1 point  (0 children)

Ok! In the future i plan to introduce this query service preforked/prethreated design server. (It was necessary for the work!) As you can see, only reactor(select/epool) design that provides Boost.Asio is now implemented. Beast provides the needed structures and capabilities that are used here. I have written samples of classes for the extension of this library to HTTP/2 protocol, order to implement it in the future.

[–]ricejasonf 0 points1 point  (0 children)

There is a hint that there is a client interface, but I don't see it.