Hi Federico,
I certainly don't mean to presume upon your free time. :-)
But of course, either of those options would be wonderful! Of the two, I think
the second function, addressing the transaction by index and label, would be
the most useful.
-- Alex
> On 2 Dec 2023, at 01:13, Federico
Hi Alex,
sorry for the late reply. I had to revisit the tsilo code, long time
without looking at it :)
When I designed the module I had in mind what I considered a "natural"
scenario for the push notifications: the entity acting as a registrar being
the one responsible for a call forking.
Of
PS. It seems to me there are some kludgy options to work around this
limitation, i.e. to basically reinvent tsilo.
They all boil down to suspending the transaction and using some sort of IPC
mechanism to queue new branch destinations, then, after some defined interval,
using some dequeueing
