Starting to get some input that there are use cases for Go language applications (such as Flogo) to be able to send (and presumably receive) tuples to and from StreamBase Input and Output Streams. Entering this as an idea for a new feature.
Here is the first such query from a TIBCO SC:
"Is it possible to publish to an input stream from a Go application? We could think about flogo but also other things...
I do not want to use messaging between my go app and SB and I know it is possible to publish to an input stream from Python... so I am looking at the same thing but from Go"
I recently assisted a field team with an RFI/RFP response that specifically asked whether we had client APIs in Go. There's another demand data point.
Gun jumped: FE-I-18
That's an argument for clarity when expressing ideas. I only put the new idea in Enterprise because the only public idea for Flogo is FLG-I-1, which is SPAM.
But just because there is an FE Idea logged doesn't mean someone couldn't create an open source one. It is, after all, just an Idea.
Steve, You're jumping the gun ;-) .... if we have the API, creating the Flogo activity/trigger function is then easy. My example was there to give weight to the idea of having the SB part so that someone can create the flogo parts, not a request for the Flogo parts.
In fact i'd rather you didn't create it, as if I create it then it will be OSS compatible, if you do it then it will get lumped with the Enterprise product
> And it would be especially nice to be able to have a Flogo Activity/Trigger for StreamBase
This is different idea than having a Go language binding for the StreamBase Client API. The client API is useful for any Go-based access to StreamBase, but this one is specific to Flogo. One idea per Idea, please! I'll go make another Idea for this one.
I wanted to do this too, solved it via messaging Flogo->MQTT->SB but it would have been much nicer to go direct to SB. And it would be especially nice to be able to have a Flogo Activity/Trigger for StreamBase.