That is not the only problem. To free the memory of the shares and to
send out further shares, also the incoming shares must be processed as
soon as possible. This is even trickier because incoming shares might
trigger code that calls functions sending out data, which activates
the Twisted reac
Martin Geisler writes:
> I'll try and write a mail to them to explain our problem in more
> detail. Maybe your short patch didn't provide enough information when
> taken out of context.
I've included a larger answer from Jean-Paul Calderone below -- you can
read in context here:
http://thread
Marcel Keller writes:
> Hi Ivan,
>
>> For instance, you call what you did a hack - is there a more
>> "official" way to do it?
>
> I call it a hack because of two reasons:
> - The maintainer of Twisted doesn't want to implement something
> similar upstream.
For those who are not on the Twisted m
Marcel Keller writes:
>> Indeed we did not know (well I didn't) back then that the data was
>> not sent immediately by Twisted, and I was starting to think
>> yesterday whether the hack would make a difference. Lucky for us, it
>> apparently does :)
>
> That is not the only problem. To free the m
Marcel Keller writes:
> Hello friends of VIFF,
>
> I've now run the benchmark of actively secure multiplications with
> hyperinvertible matrices together with my hack. Here are my results
> (column 1 and 2) compared to the results in the paper "Asynchronous
> Multiparty Computation: Theory and Im
