What is the actual problem in RTTI? Anyway, it's an implementation detail.
As you said: JSON or MsgPack base types are a fixed set, so there is no issue of forgetting stuff.
Rgd dynamic memory allocation: how do you process incoming JSON without the former? A JSON string isn't even length prefixed, so there is no way of getting rid of malloc down somewhere ..
One perspective I was contemplating about was adding a 3rd option for WAMP serialization that does in fact do away with it altogether .. the Cap'n'Proto approach
Sent from Mobile (Google Nexus 5)
--
You received this message because you are subscribed to the Google Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autobahnws+...@googlegroups.com.
To post to this group, send email to autob...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autobahnws/121bbe79-4500-4bd6-8e87-2157d767da01%40googlegroups.com.
Rgd dynamic memory allocation: how do you process incoming JSON without the former? A JSON string isn't even length prefixed, so there is no way of getting rid of malloc down somewhere ..
One perspective I was contemplating about was adding a 3rd option for WAMP serialization that does in fact do away with it altogether .. the Cap'n'Proto approach
One perspective I was contemplating about was adding a 3rd option for WAMP serialization that does in fact do away with it altogether .. the Cap'n'Proto approach
Where is the current code "verbose and unwieldy"? The code is next to
trivial.