Ah, right, fair enough. It's not important to remove the config 
reference right now. We might change it moving forward, though, esp if 
we do what we've talked about before w/ having two separate 
PipelinePack pools, one for the main loop and one for the MGI. If we do 
that, it might make sense to have each pack have a reference directly 
to the recycle channel, since it might be a different channel for 
different packs.

On Mon 08 Apr 2013 07:41:31 AM PDT, Mike Trinkala wrote:
> In pipeline/config.go:
>
> > @@ -45,6 +45,9 @@ type PluginHelper interface {
> >  	PackSupply() chan *PipelinePack
> >  	Output(name string) (oRunner OutputRunner, ok bool)
> >  	Router() (router *MessageRouter)
> > +	FindFilterRunner(name string) (fRunner FilterRunner, ok bool)
> > +	AddFilterRunner(fRunner FilterRunner) error
> > +	RemoveFilterRunner(name string) bool
>
> The PipelinePack still needs access to the RecycleChan. So the Config
> cannot be removed without adding a helper interface or reference to
> the RecycleChan.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mozilla-services/heka/pull/87/files#r3695433>.
>