search

tessel / t1-runtime

[UNMAINTAINED] Tessel 1 JavaScript runtime.
Other
117 stars 33 forks source link

Domain module: unsupported? #106

Open kevinswiber opened 10 years ago

kevinswiber commented 10 years ago

Howdy.

I make use of the domain module. I see on the compatibility page that there are no plans to support it.

I can conditionally require it deep in my dependent libraries, but I'd rather not if I can help it. Luckily, the only domain-using dependency in the code I'd like to run on the Tessel happens to be pipeworks, which is a library I created. I imagine I won't always be so fortunate.

May I ask...

  1. What are the reasons the domain module will not be supported?
  2. At the very least, would it be possible to create an API-compatible domain module that doesn't deliver on the promise of domains but still allows code to run?

I ask the first question because I'm not familiar with Lua bytecode or any limitations that would come from using a tool like colony.

The second bullet point probably requires more explanation. Basically, I guess this would mean the error event never fires; uncaught exceptions would still propagate to the process level.

Thanks!

tcr commented 10 years ago

Implemented (partially) as of #569.

natevw commented 10 years ago

c.f. https://groups.google.com/d/msg/nodejs/reTInaFyC2s/HGzwnMQ91gcJ ("I’m not on the core team… That said… it’s probably smart to continue to consider domains an unstable API, with the potential of future deprecation.")

rwaldron commented 10 years ago

@tcr Why do you say "partially"? That's the complete Domains module.

rwaldron commented 10 years ago

Nvm, I see now