/
fluid-work IRC Logs-2014-01-02

fluid-work IRC Logs-2014-01-02

[12:05:40 CST(-0600)] <colinclark> yzen: Are there some tests in Kettle that show the use of the new socket.io functionality?

[12:05:47 CST(-0600)] <colinclark> Or have we implemented it in the Flow Manager yet?

[12:05:53 CST(-0600)] <colinclark> I'm curious to take a look tonight after work...

[12:06:06 CST(-0600)] <yzen> yes there are tests both in kettle and universal

[12:06:10 CST(-0600)] <colinclark> awesome

[12:06:13 CST(-0600)] <yzen> session tests in kettle

[12:06:16 CST(-0600)] <colinclark> I built a little music controller over the holiday that sends OpenSoundControl messages

[12:06:20 CST(-0600)] <yzen> and universal update tests in flow manager

[12:06:34 CST(-0600)] <colinclark> and I've hooked it up to a Flocking synth running in Node.js and it works pretty nicely

[12:06:44 CST(-0600)] <colinclark> next step would be to hook it up to a Flocking synth running in the browser (smile)

[12:07:56 CST(-0600)] <colinclark> awesome, thanks yzen

[12:08:00 CST(-0600)] <yzen> sounds really cool

[12:08:02 CST(-0600)] <yzen> np

[14:58:22 CST(-0600)] <colinclark> yzen: Is it viable to start up a Kettle application without defining a server of any kind?

[14:59:11 CST(-0600)] <yzen> hmm

[14:59:12 CST(-0600)] <colinclark> I'm trying to understand the nature of a "config"--whether it represents a set of overrides on some kind of base configuration for an app

[14:59:21 CST(-0600)] <colinclark> or whether it is actually just "the configuration" if you see what I mean

[14:59:41 CST(-0600)] <yzen> well an app is a way to declaratively specify handlers for the http server

[14:59:56 CST(-0600)] <yzen> so http server will not be started without the server

[15:00:05 CST(-0600)] <colinclark> Sorry, I should be more careful in my use of terminology

[15:00:19 CST(-0600)] <colinclark> So these lines here: https://github.com/colinbdclark/picat/blob/master/configs/development.json#L7-L10

[15:00:30 CST(-0600)] <colinclark> Do they mean "please give me a server like this"...

[15:00:44 CST(-0600)] <colinclark> or do they mean "please override an existing server's configuration with the following details?"

[15:00:48 CST(-0600)] <yzen> oh well yes you need to specify a server at some level as a container for the app

[15:00:49 CST(-0600)] <colinclark> if you see what I mean

[15:01:08 CST(-0600)] <colinclark> But could you make a "kettle application" without specifying a server or an app at all

[15:01:11 CST(-0600)] <colinclark> ?

[15:01:23 CST(-0600)] <yzen> colinclark: we did not get to having a default server started without specifying it, so you can have more than one

[15:01:31 CST(-0600)] <colinclark> ok

[15:02:00 CST(-0600)] <colinclark> So this really is the "base configuration" for my "Kettle application" here, as opposed to some overrides of an existing set of configuration defined by Kettle, right?

[15:02:39 CST(-0600)] <yzen> yes

[15:02:45 CST(-0600)] <yzen> so for example

[15:03:06 CST(-0600)] <yzen> you can have a config where you specify an empty server with an empty app

[15:03:27 CST(-0600)] <yzen> you can then include it into another one, where then you only specify the overrides

[15:04:51 CST(-0600)] <colinclark> ok

[15:05:00 CST(-0600)] <colinclark> So let's say I wanted to define a process that didn't respond to web requests...

[15:05:30 CST(-0600)] <colinclark> but perhaps was a "scraper" or something that, every hour, went out to a web page and scraped data from it and saved the results as JSON in a Couch database

[15:05:43 CST(-0600)] <colinclark> this is a totally fabricated scenario

[15:05:51 CST(-0600)] <colinclark> but it would be a Node.js app that isn't a server

[15:05:58 CST(-0600)] <colinclark> could I still use aspects of Kettle...

[15:06:13 CST(-0600)] <colinclark> such as the "IoC trees in configuration files" and, say, DataSources

[15:06:24 CST(-0600)] <colinclark> independent of actually having some kettle.server listening on some port?

[15:06:36 CST(-0600)] <yzen> yes

[15:06:43 CST(-0600)] <colinclark> ok, great

[15:07:02 CST(-0600)] <yzen> the config file is really just a grade defaults material

[15:07:11 CST(-0600)] <yzen> which it gets turned into

[15:07:12 CST(-0600)] <colinclark> right

[15:07:19 CST(-0600)] <colinclark> that's what I was hoping was the case

[15:07:26 CST(-0600)] <colinclark> I'm looking forward to helping document Kettle

[15:07:31 CST(-0600)] <yzen> cool

[15:07:33 CST(-0600)] <colinclark> you've done a really nice job on it so far

[15:07:40 CST(-0600)] <yzen> thanks