Thanks Andrew for your reply.
As the starter of, what has become a wildfire of a thread here, I thought I'd chime in.
I've been monitoring the progress of this thread since I posted it and I still believe Asynchronous loading should be a top priority and is vital to speeding page load speeds.
And if Revive wants to be at the forefront of ad servers (which it should be), it needs to be built in.
As Redstorm stated above, page rankings are severely affected by page load times.
Yes, coders have always been able to modify, work-around or adapt, as some suggestions have been posted (which by the way are great work in the right direction), but ultimately, universal usability is going to be the Revive strong point.
Create something that doesn't get in the way of the design and usability (non-asyc currently does just that) and your market for developers has then opened up to nearly anyone looking for a competent alternative.
I can't stand Google DFP, OpenX is a joke (don't even get me started), and what are you really left with?
Revive has a chance to become the Unix/Unbuntu of the ad server world, but maintaining universality will be key in keeping the project at the top of the list.
I have been using OX, OAds, etc since it was still PHPads (can't recall what generation it was when I first started using it, but since early 2000s) and believe, it has the potential to be a far better ad server over the "services" provided out there.
Sans the monetized atrocity that OpenX became, OpenAds/Revive has always been about being the ad server that WORKS for those that don't want to use the alternative "services" out there.
No site admin wants to research, rewrite, or modify the invocation codes, they simply want to put it in place and manage inventory, and not have to be concerned that their "workaround" may break or degenerate to an unusable state, because the software is updated or changed.
Make it work, make it work right, keep it transparent within a site, and make it so ANYONE can use it.