Hey Kenton,
this was exactly what I tried to do, but it does not work as intended I
think. At least the done() call will never be received in my experimental
approaches. Especially if it contains arguments like the size of the
message it might be crucial to fix this.
For your interest regarding the iterative approach its pretty simple the
reverted recursion. Basically, every recursion can be broken down to the
iterative approach, it is not always as nice though, here it does not even
make sense. However, you could imagine chaining the requests in a loop, the
results are ignored here anyway:
auto it = points.begin();
while (it != points.end()) {
auto request = stream.nextRequest();
auto point = *it;
request.setPoint(...);
request.send();
it++;
}
I finished my research on the framework and am really happy with it!
However, the biggest problem I stumbled on is the different state of the
supported languages. We will definitely discuss it as an option, but not
sure it already fulfills all the requirements we have.
Anyway, great thanks for the fast responses and good luck on continue to
push it!
Best regards
Vitaliy
--
You received this message because you are subscribed to the Google Groups
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/capnproto/cdc70a1d-0d13-4c13-ad7a-4c2e4815e3ce%40googlegroups.com.
