The HTTP IN documentation is pretty terse, i have it working but is seems a but clumsy to use 2 HTTP IN’s to get different kinds of values into the imp. The discussions mention “channels” and i can see those used as parameters in the url but I cannot find an explanation on the planner side of the of the channels. Any tips ?
We had plans to make the # of channels per HTTP Input scalable, so you could hook up pipes to each channel and just vary the channel parameter in the URL to send to different pipes.
Instead, we’ve decided to pursue a far more flexible approach that’s coming soon. Stay tuned!