Of course, running localhost you can do even a little bit better than WebSockets. I once threw together a small app in Qt that wrapped WebKit, with a JavaScript API for message passing. Node could launch the app, or the app could launch Node, but either way, the two could then communicate with each other over stdin/stdout. It worked quite well, really!
Unfortunately, the code is a bit old and never was quite right on Windows (this was pre-0.5 Node, the only Windows support was through Cygwin), and is way too messy/encumbered in project-specific code to be released, but it's certainly a feasible and not even all that challenging option! -Matt On Feb 12, 2012, at 3:30 PM, Jann Horn wrote: > 2012/2/12 Liam <[email protected]>: >> On a public Internet link with a 40ms round trip time (common) between >> terminal & host, users will notice the response delay, so this >> approach is only suited to LAN or PAN contexts. > > True, but in the context of this thread (GUIs for node apps running on > localhost), that shouldn't be a problem. > > -- > 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
