I already designed and implemented the feature as being "completely optional".
The point is if the community approves that runtimes may be used as websocket servers (reusing the runtime machinery) deploying them in Kubernetes (they are docker containers after all) or the community prefers that OpenWhisk Runtimes are meant to be used only within OpenWhisk. -- Michele Sciabarra [email protected] ----- Original message ----- From: Bertrand Delacretaz <[email protected]> To: [email protected] Subject: Re: [Long] I implemented websocket support for the Golang and related runtimes: Date: Tue, 22 Jan 2019 15:48:52 +0100 Hi, I have very little knowledge of OpenWhisk internals so bear with me if this is not practical - but from a community point of view: On Tue, Jan 22, 2019 at 3:38 PM Michele Sciabarra <[email protected]> wrote: > ...Again, all of this is a proposal. I won't be upset if there is not > agreement.... I think in Open Source projects the way to resolve such cases when one needs something that other's don't want or have no use for is more modularity. If the impact of Michele's changes on the OpenWhisk core can be reduced to a bare minimum, maybe the Websockets functionality can live alongside it as an optional module? Note also that many Apache projects have a notion of "contrib" modules which happily live alongside a project's core module but with no guarantee that we will be kept up-to-date or relevant, maybe that's a useful model here. Having such a distinction makes it easier to accept things that might not be mainstream but are still useful to some users. Just my 2 cents from a community perspective. -Bertrand
