bidirectional

Each eLink port only supports 1.6GB/s bidirectional traffic, giving a total of 6.4GB/s of aggregate chip bandwidth.

People have been doing it for years, bidirectional methods have only started to get used in production very recently.

At least that's my understanding; I've only implemented simpler algorithms and read a bit about bidirectional path tracing.

On your list of points: * Bidirectional path tracing and VCM, surely is nice, but you're absolutely fine with just path tracing.

So there are two different things there, bidirectional tracing without and with VCM.

Also worth noting, in Mac OS X and other BSDs pipes are bidirectional.

The main challenge with bidirectional browser communication is really in the backend.

It would be great if the gravity system was bidirectional, so that you could just flip it upside down instead of lifting the weight each time.

> * Bidirectional path tracing and VCM, surely is nice, but you're absolutely fine with just path tracing.

Even if the connections weren't bidirectional you'd have 2 connections.

I know there were good reasons why TBL didn't go with bidirectional links, but we are still paying for it to this day.

Sleep and Alzheimer disease pathology - a bidirectional relationship.

Bidirectional path tracing doesn't do anything clever to "try to connect" paths from light sources and cameras.

The author seems to be getting at something very similar to the notion of "bidirectional programming" [1][2].

Bidirectional path tracing and VCM do not carry any addition complexity from an artist's point of view.

Bidirectional path tracing is one way of sampling paths (actually it combines many techniques for sampling paths and weights those using something called Multiple Importance Sampling).