Oh, so you want to distribute a dashboard to a few devices :) What a marvelous idea! So, let's play with it, I'm already enjoying this!
I'd say your key data structure is a "Car". It has a few "sensors", a "PIN", and a list of connected "display devices". If it has devices (phones) connected, it will, in order of priority, send each of them just one specific type of sensor output. It will also tell that device which output it is. Example: no phones - no output. Then a single phone connects to the server, and gives this car PIN. (Could be a password, token, QR code, whatever, I'm simplifying here). When the server sees this PIN, it starts sending to this device the most important output (engine/coolant temperature, let's say). And if you're using something like websockets, or server-sent events, or push or by simple long-polling, it updates this data frequently or in real time, depending on your sensor inputs. Then the second phone connects, with the same PIN. The server sees the second device, it sends it the _second_ type of sensor output, and starts pushing data - in our case, speedometer. And so on - as new devices connect, they are assigned a different sensor output and they start showing it. Devices, ideally, should know how to display all of the outputs, but only show the selected one, the one they receive (because you can't control the order of devices connecting). Alternatively, devices can ask for just specific sensor (e.g. RPM or signal lights) and the server will still keep track of which output to show to which device. You can connect more then 5 phones, and server tells the extra ones to be on "stand-by" - if one of the busy phones disconnects (e.g. battery empty), server tells one of the stand-by ones to chime in. I mean, you can go way less than that, for a basic functionality, or much more complex, depending on what you need. But yes, you can definitely do it and node could be the best tool for the job. On Thu, Oct 6, 2016 at 4:58 PM, thebluearchernc <jrwei...@gmail.com> wrote: > > <https://lh3.googleusercontent.com/-qv26_VPYcLE/V_ZloAAivrI/AAAAAAAAAJM/2zeigtQLmMA4JUunuPQGxxambHRbcbFlQCLcB/s1600/test%2Bdash.bmp> > > > <https://lh3.googleusercontent.com/-qv26_VPYcLE/V_ZloAAivrI/AAAAAAAAAJM/2zeigtQLmMA4JUunuPQGxxambHRbcbFlQCLcB/s1600/test%2Bdash.bmp> > Well i am new at this so no i did not know i did not need separate ports > but you are correct i wish to show part of the page on each devices with > the devices lined up to make a larger display sort like this image with > each display containing a section of the dash > > any pointers to where to begin will be greatly appreciated at this point > i do not know the exact amount of display i will need just want to make > sure this can be done. > > > > > > On Thursday, October 6, 2016 at 10:41:41 AM UTC-4, Zlatko wrote: >> >> Having 5 devices connect to different ports is fine, not a problem, but >> *why* do you want separate ports? >> >> You can have a single page and have it split into sections and have them >> all update. You can, at the same time, have 5 things connected somewhere. >> You can even make a link between those connections and the sections on the >> page. >> >> But what you're describing is very vague, so whether your specific idea >> is possible cannot yet be answered. However, create a digital dash for an >> automobile definitely can be made, with Node or whatever else. (I know >> because I was working at a connected car startup and we did these things >> with Node). >> >> So - about that page. Where do you wanna show this dashboard - on each >> android device or each device gets its own "section" of the page? I'm >> assuming you want to link 5 devices to the 5 page sections - why do you >> need separate ports? You can have a single app listening on single port, >> but keeping track at which and how many devices are connected. And you can >> have the app also keep track of those "sections" of the page, and update >> accordingly. >> >> So, share more details for more detailed answer, please. >> > -- > Job board: http://jobs.nodejs.org/ > New group rules: https://gist.github.com/othiym23/9886289#file- > moderation-policy-md > Old group rules: https://github.com/joyent/node/wiki/Mailing-List- > Posting-Guidelines > --- > You received this message because you are subscribed to a topic in the > Google Groups "nodejs" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/nodejs/TPIPuh1TieE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > nodejs+unsubscr...@googlegroups.com. > To post to this group, send email to nodejs@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/nodejs/792861dd-9f4c-4d5c-9826-cc0aba425a4a%40googlegroups.com > <https://groups.google.com/d/msgid/nodejs/792861dd-9f4c-4d5c-9826-cc0aba425a4a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Zlatko -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CADu3pbwEp7W8k-mvrHvv17a%2BsT_774cxFt5FMmPYGS1dOryz8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.