Generalized hook interface?

[jeremytregunna]

Is there any thought going on or something I've maybe missed about writing custom outputs for hooks? As in, we can define webhooks right now, but in my application, I don't use HTTP at all, and would like to be able to call back to clients via some other protocol. To support this, there'd need to exist some generalized hook interface that could support multiple protocols. Is this something that is interesting enough to consider?

[tidwall]

As it stands right now, there are no plans for a generalized hook interface. Currently Tile38 supports HTTP, WebSockets, Disque. There is also the ability to connect directly to a raw socket which would allow for a middleware microservice to deliver messages in a custom manner.

That being said, I suppose it's not too far fetch to add support for more protocols. Out of curiosity, which protocols do you have in mind?

[jeremytregunna]

@tidwall I'm working with MQTT at the moment.

[tidwall]

Commit 3b99a62 includes the first steps to a more generalize interface for Hooks. The root package is in the controller/endpoint directory. There's still more work to be done, but it's a start.

[tidwall]

The custom endpoint interface is stable has been in use in production for a few months. I would be more than happy to advise anyone who wants to add a custom implementation such as MQTT.

[tidwall]

It may also be worth noting that with next release of Go 1.8 could possible extend the custom endpoints to support Go Plugins

[tidwall]

The Go Plugins isn't as great as I hoped. It's not cross platform and requires cgo attributes. For now we'll need to stick with current process of adding new hooks. The recent Kafka PR is good example.

I do think we should add MQTT support though and added a feature request to #154.

[tidwall]

@jeremytregunna Not sure if this is still something you're interested in but there's a MQTT PR in the pipeline #155. Any feedback would be greatly appreciated. Thanks!