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 <[email protected]> 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 collect a process / thread ID for uniquness > > It should be a language construct. The API I would prefer would be > > process.tickId > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
