thanks for your reply. Basically it's a radar application which requires lots of DSPs and external interface such as GPS and navigation data. But it sounds like not a good idea at the moment. Thanks though.
On Monday, September 24, 2012 8:19:36 AM UTC-7, Ben Noordhuis wrote: > > On Mon, Sep 24, 2012 at 4:58 PM, LuckyLuke <[email protected] <javascript:>> > wrote: > > Hi, > > I'm investigating the possibility of using Node in a real-time embedded > DSP > > application. > > General requirements: > > - Multiple CPU cards in an OpenVPX chassis (in a deployed system) or > > - Multiple CPUs on a Development system (s/w should abstract h/w config) > > - Multicores on CPU (Intel Sandybridge or equivalent) > > - C++11 to handle multi-thread on cores (or just Pthreads but C11 seems > > promising) > > - Node as event-driven task management and as "communication" > middle-ware > > where communications can be > > -- from a GUI (browser based) > > -- CPU cards to cards > > -- CPU to CPU > > > > Am I on the right mind even considering this architecture? > > thanks all. Node Rules! > > You describe what this machine has, not what it's supposed to do. I'll > try to answer your question, though. :-) > > node.js makes no claims to being real-time (in the hard real-time > sense). Don't use it to drive a MRI scanner. If it's to drive a GUI, > you should be fine. > -- 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
