As it stands now, we have a pure java wrapper application that simply starts a subprocess with our pure go binary. I guess what you are saying is that our Go application needs to become a library, rather than a process. Which is complicated as I am not sure it can, as our cleanup assumes the process gets killed, which in this case would not be possible, so with every invocation we might leave more and more trash in the runtime.
I wonder if passing the fds using unix sockets from java to go is not the easier option. Also, having a go binary that gets the vm instantiated somehow and then reverse binding to get the fd would be my other prefered option, yet I don't think its possible without an activity. I guess we could spawn a noop activity in the subprocess but I am not sure how that would work. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
