> If we have a `binary` runtime for Go, can this also be used with other > static binaries if they support the correct API endpoints? If so, we > could have a generic binary runtime to support more languages. I definitely think yes.
In my opinion you can have 2 ways of supporting native actions. One is with the "popen" that will start another process. Another is with the replacement, the one I am trying to implement. However I think it is possible to have something in the middle, for example with a named pipe. An executable may then be started as a child process, for example, reading continuously the input in the file descriptor 2 line by line and writing in fd 3. Or maybe using IPC. After implementing the Go support we can see if this is also possible. > > > On 10 February 2018 at 16:37, Carlos Santana <[email protected]> wrote: > > details details ... > > > > Will help along the way > > > > Yay !! OpenWhisk Go! > > On Sat, Feb 10, 2018 at 10:57 AM Rodric Rabbah <[email protected]> wrote: > > > >> > One problem I see is the /run running on port 8080 there will be a port > >> conflict. > >> > >> Michele said "exec", so the initial proxy will replace itself with a new > >> proxy and the compiled function. > >> Should avoid port conflict. A wrinkle I see is terminating the /init > >> connection held by the invoker (so this has to be orchestrated properly). > >> > >> There might also a need to retry the /run in case of a failed connection > >> (because new proxy isn't up). We had disabled this explicitly at one point, > >> but I don't foresee a show stopper yet. > >> > >> -r > >> > > > > -- > Regards, > James Thomas
