Mimic VS Boost.Beast

It might be possible but it may not be the best choice for a beginner project. By using efficient use of attach() and detach() calls I built and coded up a 4-servo robotic arm that runs on just two-18650's (Mimic), but again it's not something you should try as a first project unless you have a decent understanding of stuff like Kirchhoff's Law &c.

Several years ago I made an arduino based arm and I wanted to do exactly what you are talking about so I included the ability loadstore and reload the arm movements from EEPROM. The project and source code are here and you should be able to re-use the EEPROM storage and retrieval parts of the code (or more maybe).

That still very cool and I love the oragami idea! I've looked into oragami for sources of inspiration for different kinds of leverage although I can't say I completely understood the math. 🤪 That's too bad about your 3D printer. I made a simpler robot arm that used 4 servos and I used popsicle sticks to make mine heh.

I wrote exactly what you're describing for the Arduino *I think* and here's the sauce.

I wrote something like this a few years back. It is a robotic arm that let's you control it using an identically shaped arm that has potentiometers at each joint instead of servos. So one arm 'Mimics' the other. The code for reading, controlling, and recording the movements to EEPROM is there if you want to grab anything. Also, you mention needing to get your button code correct and that same project has an interesting button library I wrote that let's you multiplex one button into tons of different selections by letting you define any combo of (up to 3) short and long button presses and configuring what function to run for that "buton gesture". You might find that useful (or maybe confusing the code isn't ideal for learning from haha).

There is at least one notable exception to this rule: https://github.com/boostorg/beast/issues/1445

I am using this example : https://github.com/boostorg/beast/blob/develop/example/websocket/client/async-ssl/websocket_client_async_ssl.cpp My application is listening to tick data streams of crypto exchanges over the websockets and processing and sending orders to the exchange.

We used beast to implement a market data server(and I think we also did a small client, to test it) which was sending protobuf messages, and it worked great(we also used boost adio, which made it very scalable). When we tested the server, we were generating around 100k messages per second(when there was the biggest activity on the market), I think I've posted here some stats: https://github.com/boostorg/beast/issues/2313.

Boost Beast?

And Chris wrote this example, which is faster than any of my other examples: https://github.com/boostorg/beast/tree/21cd552399aa8167ed53c21a74f3711c2c316d2f/example/http/server/fast

cmake -h. -Bbuild && cmake --build build

to work about 90% of the time. Far more luck than I've had with autotools.

> Its code is horrifying too, for example:

1) I'm sure I could find some horriffic code in meson too if I went digging. 2) The alternative to this is you having to write something equivalent in your own code, meaning that in my code I don't need to do stuff like [0] in my code to detect features; my build system handles it for me. 3) CMake supports more platforms and targets than I've ever seen in my life, and likely supports more compilers than are necessary. that's a blessing and a curse, but it means that if I write simple program to run on some crufty microcontroller with a bastardised gcc toolchain from the 90s, it's fairly likely that cmake supports it out of the box. Code like that is the price to pay for that level of support.

[0] https://github.com/boostorg/beast/blob/b7344b0d501f23f763a76...

If you need an embedded C++ HTTP server then there are plenty of libraries/frameworks (in random order): Crow, RESTinio, Boost.Beast, cpp-httplib, http_backend, Pistache, RestBed, served, proxygen, Simple-Web-Server, drogon, oat++.