On Jan 24, 2014, at 3:11 PM, Mark Hahn <[email protected]> wrote:
> I have no problem using phantom as a child process. You can communicate with
> it while it is running. I would imagine one could write a module to make the
> interaction quite transparent.
>
There are some modules, I think, that in fact claim to implement what you
suggest. I just interface directly with PhantomJS using child_process (but oh
what I would give to get my trusty Unix fork()/exec() back!). I agree that this
method is quite usable, but in the child process I often catch myself adding
node-like code out of habit only to have it crash. Which is a small nit. I am
happy with PhantomJS.
—ravi
--
--
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
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
