ports implicitly buffered with WirePattern

[djdeath]

NoFlo input ports are implicitly non buffered : https://github.com/noflo/noflo/blob/master/src/lib/InPort.coffee#L17

But using WirePattern implicitly buffers the data of the port. Shouldn't WirePattern respect the config of the port?

[djdeath]

Here is an example : https://github.com/noflo/noflo-gnome/blob/master/examples/2048/components/SquashTiles.coffee

The map input port being a parameter, no processing occurs until the data is received.
Once it arrives, all the directions received are processed. I would expect that only the last one would be processed, since it's a non buffered port.

[trustmaster]

WirePattern does not use built-in port buffers, however it maintains several buffers of its own to synchronize incoming data. Marking a parameter as required makes the component wait for that parameter before processing any input. If we change it to drop all the input before all required parameters are received it would cause unexpected loss of data in many cases, or many components will likely have to set buffering: true on their ports.

Alternatively, an option could be added to WirePattern to drop premature data instead of buffering it. Does it have to be port-specific or could it work for entire component?