> > *Thank you for your answer. * > *Do you know if I will be able to do the same stuff with a server on one > side and an html on the other to display real time acquisition ? * > > *It is a 3 month project I realy feel like I lost a month implementing all of this with Java script.*
There are several ways you can approach this. One that sticks in my mind would be to: a) Use a compiled language such as C/C++ to do the actual data acquisition. The application would then write values with perhaps timestamps to a file created in memory. b) Nodejs with fs.watch() method + socket.io.to stream data to the client browser. Where client side javascript can deal with all the heavy work. So, while there may be some latency between the actual data acquisition application, and the client side browser. The data could be displayed in a reasonably timely fashion. With time stamp information. However, it is also a reasonable assumption that if you need to make real time "adjustments" from the client side . . . this would not work so well. socket.io may be what some consider "real-time" but the reality is that there are sometimes, and sometimes often latencies of 100ms + between server / client. Even on a closed local network. On Wed, Jun 10, 2015 at 5:46 PM, <[email protected]> wrote: > Thank you for your answer. > > Do you know if I will be able to do the same stuff with a server on one > side and an html on the other to display real time acquisition ? > > It is a 3 month project I realy feel like I lost a month implementing all > of this with Java script. > > Thanks again. > > Best regards, > Matthieu Hoel. > > > Le jeudi 11 juin 2015 05:33:37 UTC+8, Przemek Klosowski a écrit : >> >> I think javascript is not the best implementation platform for this >> code because you need guaranteed latency, even though 8ms period is >> not very demanding. You could try playing with the interpreter process >> priority and scheduling algorithm, but in the end you probably should >> start looking at implementing this in a compiled language (C/C++). >> >> On Wed, Jun 10, 2015 at 4:38 AM, <[email protected]> wrote: >> > Hy again >> > >> > -- >> > For more options, visit http://beagleboard.org/discuss >> > --- >> > You received this message because you are subscribed to the Google >> Groups >> > "BeagleBoard" 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/d/optout. >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" 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/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" 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/d/optout.
