Re: [wallaroo - Goland] - Go API documentation and samples
HI Sean Thanks for the information . wrote:
By
Jasintha Dassanayake
·
#148
·
|
Re: [wallaroo - Goland] - Go API documentation and samples
It's something that we would discuss. If it all passed with the latest master, we'd probably merge it but, I couldn't promise ongoing support. We stopped developing the Go API so we could move quicker
By
Sean T. Allen <sean@...>
·
#147
·
|
Re: [wallaroo - Goland] - Go API documentation and samples
We haven't had any Rust conversations. It isn't something that anyone has requested. If someone in a commercial relationship requested it, it would be something we considered. wrote:
By
Sean T. Allen <sean@...>
·
#146
·
|
Re: [wallaroo - Goland] - Go API documentation and samples
Hi devs If we migrate Go APIs into the latest version (0.6.0) and send a PR, will you guys accept and merge it? Thanks Jay <dassanayake@...> wrote:
By
Jasintha Dassanayake
·
#145
·
|
Re: [wallaroo - Goland] - Go API documentation and samples
Hi Sean Thanks for the quick reply, then we will be using pony or python, BTW, is there any plan to support RUST in the future? thanks /Jay -- Jasint
By
Jasintha Dassanayake
·
#144
·
|
Re: [wallaroo - Goland] - Go API documentation and samples
Hi Jay, We aren't currently supporting the Go API. There wasn't much demand for it. We'd be willing to entertain support on a commercial basis. For the open source, version, we have Python support as
By
Sean Allen <sean@...>
·
#143
·
|
[wallaroo - Goland] - Go API documentation and samples
Hi Devs We are a startup and working on a software platform. We have decided to use wallaroo as a stream processor in our platform. We would like to try out the Go API instead of using python or pony
By
Jasintha Dassanayake
·
#142
·
|
Re: Wallaroo connector
The connector protocol is language agnostic. You can write a connector in any language you want, not just Python. For a specific connector, you could pickle the data and send it across as long as you
By
Sean T. Allen <sean@...>
·
#141
·
|
Re: Wallaroo connector
Thanks for the prompt reply Why not default to pickling for connector encode/decode ? as communication between worker already default to pickling.
By
nuhamind2@...
·
#140
·
|
Re: Wallaroo connector
Hi. Answers inline below. So I manage writing connector for nats server (after digging through the Connectors are all external processes. You could write a NATs source in Pony that runs directly in
By
Sean Allen <sean@...>
·
#139
·
|
Wallaroo connector
Hi Just wanting to ask, what is the benefit of writing connector in pony rather than python ? So I manage writing connector for nats server (after digging through the source code), then I found that
By
nuhamind2@...
·
#138
·
|
Re: Need Wallaroo help? Talk to me
Hi Audun It's clear to me that what you want is a Connector <https://docs.wallaroolabs.com/python-tutorial/using-connectors/>. You'd have a connector process that opens a python socket to the data
By
Simon Zelazny
·
#137
·
|
Re: Need Wallaroo help? Talk to me
On Fri, Jan 18, 2019 at 4:29 PM <audun.stolpe@...> wrote: > Yes, I know that's the intended use of GenSourceConfig. I just tweaked the > mode of generation to be that of > popping elemtns off a
By
Simon Zelazny
·
#136
·
|
Re: Need Wallaroo help? Talk to me
Yes, I know that's the intended use of GenSourceConfig. I just tweaked the mode of generation to be that of popping elemtns off a TCP stream. ? I'll provide you the details later if necessary, but in
By
audun.stolpe@...
·
#135
·
|
Re: Need Wallaroo help? Talk to me
Can you explain a bit further what you mean by this? What are you passing into wallaroo.GenSourceConfig? wallaroo.GenSourceConfig is meant to accept a class which autogenerates messages for Wallaroo.
By
Jonathan Brown
·
#134
·
|
Re: Need Wallaroo help? Talk to me
Sorry mistyped, the port was 7010 in both instances. Thanks for the link I'll read up. In the meantime I managed to hook up the stream by using? wallaroo.GenSourceConfig and then just popping one
By
audun.stolpe@...
·
#133
·
|
Re: Need Wallaroo help? Talk to me
On Fri, Jan 18, 2019 at 9:39 AM <audun.stolpe@...> wrote: > I started the Wallaroo module: > > #!/usr/bin/env python > import os > > instruction=("machida " > "--application-module tester " >
By
Sean Allen <sean@...>
·
#132
·
|
Re: Need Wallaroo help? Talk to me
I started the Wallaroo module:? #!/usr/bin/env python import os ? ? instruction=("machida " ? ? ? ? ? ? ?"--application-module tester " ? ? ? ? ? ? ?"--in 127.0.0.1:7010 "? ? ? ?
By
audun.stolpe@...
·
#131
·
Edited
|
Re: Need Wallaroo help? Talk to me
Sorry, can you go into more detail what you did with `nc` including what other commands you ran and what happened? -- Sean T. Allen VP of Engineering WallarooLabs.com *Unlock Data's Potential.*
By
Sean Allen <sean@...>
·
#130
·
|
Re: Need Wallaroo help? Talk to me
In fact, if I just do nc 127.0.0.1 7010 (corresponding to the adress specified as input source) then my wallaroo module acknowledges the connection, but no data I send over it gets through. A
By
audun.stolpe@...
·
#129
·
|