If we send launch params to the roku, it will relaunch the app, even if it is already running. What if I want to know if I want to send the launch command, or just send some parameters to the currently running app, is there a way to tell if something is running?
I believe that’s what the new socket components are for.
-JT
hmm - the socket example app crashes on load…
I haven’t tried it and to be honest I know very little about sockets. I just thought they were a way to connect to your channel while it’s running.
Edit: Ok, I tried it and it looks like the firmware and documentation aren’t ready for prime time. If the server will bind to a port, which happened like once out of a dozen tries, SetMessagePort isn’t a valid function (and neither is GetID, by the way). Looks like we’ll have to wait on this one.
-JT
My limited examination turned out the same way. I think the interface components available may actually differ depending on how it’s created, but I haven’t had a chance to revisit it.
I thought the same thing, but I don’t know of any other components that behave that way.
-JT
“jbrave” wrote:
If we send launch params to the roku, it will relaunch the app, even if it is already running. What if I want to know if I want to send the launch command, or just send some parameters to the currently running app, is there a way to tell if something is running
Yeah, that functionality is missing in ECP. I already proposed extension here viewtopic.php?f=34&t=38144&p=249414#p249414 - but perhaps illustrate with example:
Query
GET /query/channel HTTP/1.0
Response
Content-Type:text/plain; charset=UTF-8
<... etc headers >
12
12 being Netflix - ok, we know what’s running now. No channel (main menu) will return 0 or some such
Any attention on this, Roku*?
