eao197
eao197
Ok. I understood. Have you tried just send `vector` as a message?
> convenient partial loss of types and restoration I have no idea how it can look at API level :(
> Is there a problem at the API level? Now everything is really simple and clear: ```c++ struct my_msg { int a_; int b_; ... }; ... void some_agent::on_my_msg(mhood_t cmd)...
But what will be inside `dynamic_msg`? How do you plan to extract some data from an instance of `dynamic_msg`?
> one of the options It's the same thing as using plain `vector`. It can be done without support from SObjectizer. > types to save at the time of registration...
Честно говоря, пока не понятно, зачем нужен еще и AppVeyor, тем более, с такими ограничениями по времени. Так что возьму некоторый тайм-аут для того, чтобы принять решение.
Thanks for your PR! There are some controversial points we need to discuss inside our team. For example I don't like the idea of embedding any third-party libraries into RESTinio...
> The alternative would be expecting most developers who use the library to completely forgo the test suite. I think there are (at least) two point of view on approach...
@ArchangeGabriel > I had to patch locally in order to allow that and successfully build restinio. Can you show your patch?
@ArchangeGabriel Thank you. I'll see what can we do to allow users to use RESTinio with already installed http-parser package.