[viff-devel] Confusing behaviour?
Thomas P Jakobsen
thomas.jak at gmail.com
Tue Mar 24 01:26:23 PDT 2009
Thanks for the reply.
> However, your problem probably could be fixed by synchronizing before
> blocking:
>
> sync = runtime.synchronize()
> sync.schedule_callback(blocking_code())
Yes, I was thinking the same thing. Another way of avoiding the
problem is to place initial local computations outside the VIFF
protocol. But I don't think its intuitive and it will probably confuse
future VIFF users too if it's not fixed or at least documented
somewhere.
Regards,
Thomas
More information about the viff-devel
mailing list