Right now, if a VAST response returns a set of companion ad sizes, the code
searches based on that
list trying to match against the companions that the user has defined in their
config.
It should the other way around as that is more efficient.
See example43 as an illustration - the VAST template has 10+ companions, but
only 2 are user
defined on the page, but the matching goes through the 10+ list ...
Original issue reported on code.google.com by paul.sch...@gmail.com on 13 Oct 2009 at 7:20
Original issue reported on code.google.com by
paul.sch...@gmail.com
on 13 Oct 2009 at 7:20