lganzzzo on refactor_object_wrapper
Types: oatpp::Void now is a spe… (compare)
lganzzzo on refactor_object_wrapper
ObjectWrapper: non-const valueT… (compare)
Do you want me to also make the String ctor to v_int64 change in this PR?
Yes, it would be cool!
Also, there are some pleases where explicit casts were applied to silent warnings... those should be deleted as well.
Unfortunately, I don't remember where exactly :)
It would be great to move all classed that use buffers to v_int64. Like MemoryLabel for example.
So I guess we can make it step-by-step. Because once you move String yo int64 to silence one bunch of warnings - others will pop up :))
... just like with any refactoring :))
@/all ,
Update :bell:
Oat++ version was increased to 0.19.10
, and the new release tag is added.
Please find the release with changes made in October here 0.19.10
ApiController
. Add router prefix.LazyStringMap
to store headers and query parameters.ConnectionPool
. You may find usage example here. Used to increase performance and, in order to prevent ephemeral ports exhaustion on the client during high load. ADDCORS
--> ADD_CORS
macro.Cheers :tada:
Leonid
RequestExecutor
for ApiClient
.
oatpp-admin
like in django. But it is a good idea to have one in future
Hello @madkote ,
I don't have any direct recommendations, but there are some points to consider:
Simple API
- then it should be very easy to use any Redis client, and the process of integration should be straight forward.Async API
- then things become more complicated because, in oatpp-coroutines, you have to user oatpp-coroutines based API. It also depends on what kind of Redis API you are planning to use...Something like that...
Please let me know if you have more questions.
DTO_FIELD(Int64, time);
};
class ResponseDto : public oatpp::data::mapping::type::Object
{
DTO_INIT(ResponseDto, Object)
DTO_FIELD(HeaderDto::ObjectWrapper, header);
};