By the way, websockets put simply, is a TCP connection between systems,
that is always connected. So there is no need for Ajax, or any of that old
school HTML mumbo jumbo.

On Sun, May 14, 2017 at 4:04 PM, William Hermans <[email protected]> wrote:

>
>
> On Sun, May 14, 2017 at 12:38 PM, Piotr C <[email protected]> wrote:
>
>> Thanks for suggestions.
>> Do you have any further hints/examples/similar implementations that I
>> could read, understand and eventually base on?
>>
>
> The code I wrote is not, and will not be available to the public.
>
> There is no real way for me to show you how to do what all needs being
> done. Here is why. By it's self, websockets is not necessarily an easy
> concept to understand let alone write code for implementation. As such the
> easiest way to get started, would be to use Nodejs and socket.io. At this
> point, you need to understand how to install, and use Nodejs + socket.io,
> as well as probably how to use Express as well. Keeping in mind that having
> to know all this is just so you can understand the basics. After this, you
> *may* be ready to move onto using websockets from a web / websocket server
> written in C, or C++.
>
> Not to mention having to know how the CANBUS protocol you're using works,
> knowing how socketCAN works under linux, and knowing how a multitude of
> other software technologies work. So you can bring it all together, to make
> your application work.
>
> So can I help you understand how to create such software ? No, not really.
> This is something you're going to need to spend a lot of time on, before
> things almost become clear as to how you need to proceed.
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORp39JugtVBNhocy4pqUmrCDKyXZpguwur3rzahHiHqO%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to