Alessio Vanni <[email protected]> writes: > I made sure to use a new envelope each time. In fact, the real > implementation is a dedicated function that does some basic checking > (e.g. make sure the pointer to the data is not NULL) before sending the > message. I tried calling it both inside a normal for loop and also as > "scheduled tasks" using `GNUNET_SCHEDULER_add_now' after each message is > sent (of course tasks were added only if there were more segments), but > to no avail: the service gets only the first segment.
I found the culprit on why only the first message is received... the client code had become a bit entangled and I lost the fact that the program is set to terminate once data is sent. Naturally doing this impedes the sending of the remaining messages. Is there a way to make the program terminate once all the messages are received? I'm sure a simple solution would be to receive a message from the service, but since the service-to-client message queue is created within the API which is a separate library, is it safe to call `GNUNET_SCHEDULER_shutdown_now' from there? Thanks, A.V. _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
