On Jun 14, 2012, at 11:02 PM, ivolo wrote:
I am wondering if there is any (performant) way to identify a unique tick in
the event loop?
I don't want to do anything like: 1) throw an exception, collect a callstack,
analyze it, and hash it, or 2) subprocess any OS or external processes to
I am wondering if there is any (performant) way to identify a unique tick
in the event loop?
I *don't* want to do anything like: 1) throw an exception, collect a
callstack, analyze it, and hash it, or 2) subprocess any OS or external
processes to collect a process / thread ID for uniquness
I can't imagine any situation where it would be a good code design and need
that.
On Thu, Jun 14, 2012 at 2:02 PM, ivolo i...@segment.io wrote:
I am wondering if there is any (performant) way to identify a unique tick
in the event loop?
I *don't* want to do anything like: 1) throw an
I doubt something like this would go into core, but if core had a supported
API for wrapping event sources, it would be trivial to implement as a
third-party module.
On Thu, Jun 14, 2012 at 6:11 PM, Mark Hahn m...@hahnca.com wrote:
I can't imagine any situation where it would be a good code
