**** BEGIN LOGGING AT Sun Jun 10 03:00:05 2018 Jun 10 09:31:08 muneeb17: Hi ! How is it going ? Jun 10 09:32:51 zeekhuge: Hi, I'm refining the code now. I will also add some more examples. Jun 10 09:33:33 I also added the config file stuff. Will push the code in some time Jun 10 09:34:09 An example .. Jun 10 09:34:33 not sure will be very intersting or not .. Jun 10 09:34:38 but .. maybe .. Jun 10 09:35:01 You can use nodejs to create a REST APIs to send and recieve message to the PRUs Jun 10 09:35:16 zeekhuge: I was thinking of the exact same thing Jun 10 09:35:27 and maybe .. PRUs can blink some of the LEDs and that .. Jun 10 09:35:47 you have experience in JS ? Jun 10 09:36:22 zeekhuge: will only need to modify the daemon a bit. Yeah, i have some experience in it, somewhat beginner to intermediate... Jun 10 09:36:24 mostly, use express as the framework .. and can route the API calss .. Jun 10 09:36:49 muneeb17: ? why modify daemon ? it wont be an example then ... Jun 10 09:37:23 what modifications btw ? Jun 10 09:37:45 zeekhuge: unix sockets to tcp sockets Jun 10 09:38:01 no ! no ! Jun 10 09:38:09 instead .. Jun 10 09:38:51 use express based nodejs code as the tcp end, and which binds to PRUSS-nodejs-bindings and thus makes call to the PRUs Jun 10 09:39:27 infact, that is what these bindings are for. Jun 10 09:39:28 they provide an interface to the daemon. Jun 10 09:39:52 and the "user-code" can implement its own interface/logic for anything it requires Jun 10 09:40:53 zeekhuge: Yeah, makes sense.... Jun 10 09:41:19 so, in the above example, (create a mental image of this) the nodejs-REST-APIs-Server will be "user code" implementing the tcp end, and in the back, binding to the PRUSS-nodejs-bindings to make calls to the daemon. Jun 10 09:43:20 zeekhuge: Yeah, got it.. will work on that **** ENDING LOGGING AT Mon Jun 11 03:00:02 2018