Thanks for the reply Bobby! We were thinking of submitting some PRs to:
* Add a maven profile that would bundle storm js in an npm package and submit it to npmjs.com. * Extend the functionality defined in storm.js to allow for bolts to manually ack. * Add some unit tests for the js code maybe? Are these things that you think belong in the multilang-javascript module? Or does that sound like something that should be a standalone project and not part of the storm code base? Thanks again for the reply, -Marc On Fri, Jul 15, 2016 at 1:28 PM Bobby Evans <ev...@yahoo-inc.com.invalid> wrote: > It was added by a group that I think was using it in production. We have > made some tweaks to it since then, but not much, > - Bobby > > On Thursday, July 14, 2016 10:53 AM, Marc Zbyszynski <mmm...@gmail.com> > wrote: > > > Hi There! > > I'm wondering what the intent of the multilang-javascript module and the > storm.js file is ( > https://github.com/apache/storm/tree/master/storm-multilang/javascrip). Is > this intended as a reference or example implementation of a node.js/storm > integration? Or are you intending storm.js to be the canonical node.js > multilang wrapper that everyone should use for real/production storm > projects that use the multilang protocol to communicate with node.js bolts > and spouts? > > The reason I ask is that my team is starting to look at adding storm > topologies to a large node.js project, and we are trying to decide whether > to use the storm.js file included in the storm distribution as our starting > point, or use a 3rd party library or roll our own. > > I haven't found any 3rd party libraries that seem actively maintained. The > storm.js file looks good, but seems to only expose a limited number of > features (no support for bolts that do not ack automatically, no hooks for > tick tuples, etc.). We'd be happy to submit some PRs to add this > functionality, and add the metadata files to make it a real node.js > package. > > Is that something you would want to add to storm-multilang? Or is that > beyond the scope of what you intended the multilang-javascript module to > be? > > Let me know what you think! > > Thanks, > > Marc > > >
