Passing vend commands via json or args

[narendasan]

Discussion to have on direction would like input from @sameetandpotatoes and @abrandemuehl

[rauhul]

@narendasan did we decide on running a RESTful server on the Pi? Eric mentioned Illinois net could cause issues.

[narendasan]

Regardless of what we decide we do need to run a web server due to our network architecture. We can get the pi cleared for the network or we could use the network switch to address those issues

[abrandemuehl]

Can we run a "Merch" service wherever the rest of the Groot services run, then keep a persistent connection to that service from the Pi?

[narendasan]

I think eric was worried about connecting to the network. As to architecture, I think the idea of ipad hits groot with hits the pi is ok and a webserver on a pi is probably the easiest way to handle the pi part

[wchill]

If the Pi is not directly connected to a wall jack, then you will run into issues with NAT since the Pi will not be reachable outside of whatever network it is connected to.

The best way to do this is have the Groot service wait for the Pi to connect to it (using regular TCP sockets, WebSockets, or perhaps using a reverse SSH tunnel and running the webserver on the forwarded port, up to you) and then pass commands over that connection. This will get around the NAT issue.

[narendasan]

We only need the pi to connect to the service which is hosted on the network

…

On Thu, Mar 23, 2017 at 4:09 PM Eric Ahn ***@***.***> wrote: If the Pi is not directly connected to a wall jack, then you will run into issues with NAT since the Pi will not be reachable outside of whatever network it is connected to. The best way to do this is have the Groot service wait for the Pi to connect to it (using regular TCP sockets, WebSockets, or perhaps using a reverse SSH tunnel and running the webserver on the forwarded port, up to you) and then pass commands over that connection. This will get around the NAT issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABtSlZhQH93Wwu4vIEFrQ3j497x-u_jeks5rovuugaJpZM4MnJ3G> .

[narendasan]

Websockets may work

…

On Thu, Mar 23, 2017 at 4:11 PM Naren Dasan ***@***.***> wrote: We only need the pi to connect to the service which is hosted on the network On Thu, Mar 23, 2017 at 4:09 PM Eric Ahn ***@***.***> wrote: If the Pi is not directly connected to a wall jack, then you will run into issues with NAT since the Pi will not be reachable outside of whatever network it is connected to. The best way to do this is have the Groot service wait for the Pi to connect to it (using regular TCP sockets, WebSockets, or perhaps using a reverse SSH tunnel and running the webserver on the forwarded port, up to you) and then pass commands over that connection. This will get around the NAT issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABtSlZhQH93Wwu4vIEFrQ3j497x-u_jeks5rovuugaJpZM4MnJ3G> .

[rauhul]

We should move to passing the vending commands via json so we can support vend queues