Plugin client won't bootstrap successfully if the first message sent from plugin is not the negotiation format.

[chenxi-neo]

I'm now using go-plugin to develop some Golang applications and it works well. Except that if the first message the client received from the plugin is not the right format like: 1|1|tcp|127.0.0.1:1234|grpc, the client will not correctly negotiate with the plugin process . This is a bit strict if some plugin written in Golang import other third party libs that print something in the init function.

may be we could add some regex filter to extract the negotiate message from the plugin output? Or do we have better solution to deal with this problem?

[skyf0cker]

This also made me confused. We cannot guarantee that the third party module is designed to have no stdout in their init functions. Maybe we should find another way to negotiate a port to use for rpc.
CC @evan2645

go-plugin/client.go

Line 503 in a88a423

func (c *Client) Start() (addr net.Addr, err error) {