sharing memory structure between tasks

[mikehaas763]

I have a serve task that starts a Browsersync server. When my tasks are done running I can then call browserSyncServer.reload() to reload the page in browsers. I'm doing this with a watch. It would be nice if I could split the watch task into its own module that is isolated from the serve task.

I should mention that these tasks are registered with a custom registry that require's the individual task functions which are located in separate modules. The custom registry uses a configuration object. I could just place a reference to the Browsersync server somewhere on the configuration object and access it from the other tasks.

Is that going to be the smoothest way to accomplish sharing data between tasks forward into the future of undertaker and g4 or have you thought about any other APIs that could make it more straight forward?

[phated]

Can you give me some code to see how you are currently doing this? That will better help me make suggestions. Thanks

[phated]

@mikehaas763 pinging

[mikehaas763]

I saw your replies, just short on time. This is still on my todo list. I'll let you know when I revisit it. Thanks @phated

[phated]

Going to close this for inactivity soon. We are getting close to shipping the 1.0 and I don't have anything to go on to look into this issue.