Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's effectively what I suggest in the other replies. You separate internal from external callbacks, and run the internal ones first and enqueue the set of external ones, then run those at the end. All subsequent externally-driven changes should be enqueued until the next "turn", ie. after all changes have settled. This preserves transactional semantics.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: