Timeline for Lazy/deferred OOP-based networking using the Epic EOS SDK
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 3, 2023 at 11:23 | comment | added | Alexovsky |
I also have a habit of avoiding "free function" because at the unitTest stage, the fixture is more accustomed to operating with struct/class and it is easier for me to locate and name tests. About std::function => std::packaged_task is brilliant. It was very helpful and I hope it will work and thank you.
|
|
| Dec 3, 2023 at 11:22 | comment | added | Alexovsky |
I didnt want to clutter the Ctx; When developing API access, you often need to store many variables in one place, the purpose of which is not yet clear. In my opinion, POD/Aggregate is ideal for this. In the case of Sending/Reception and SendText/ReceiveText I tried to semantically separate: the controversial creation functionality and the clear execution functionality. My mistake is that I did not fully resolve the controversial issues. Regarding for the "free function", I chose classes to reduce the number of call arguments.
|
|
| Dec 3, 2023 at 11:21 | comment | added | Alexovsky | Continued in asynchronous. I always strive for "Separate concerns", but I don’t always have enough concentration at the moment when it is not known where the architecture will turn, my mistake. As I wrote in the question, I try to avoid singletons and global variables, I didn’t have enough determination, my mistake. | |
| Dec 1, 2023 at 23:01 | vote | accept | Alexovsky | ||
| Nov 26, 2023 at 12:49 | comment | added | Alexovsky | I really liked the final part, I will try to implement it as soon as possible and first thing. That's what my thoughts revolved around. Most likely, this is exactly what was needed and what was missing. Thanks! | |
| Nov 24, 2023 at 23:52 | history | answered | G. Sliepen | CC BY-SA 4.0 |