AEBS (2nd Gen) WPS printing is very slow

That tutorial really doesn't do anything any different than using the WPS configuration. That tutorial is just the manual procedure for the setup. It did illuminate one possibility for the slow printing. If you simply press the ➕ sign in the print & scan preference pane and add the "nearby" network printer you desire then it defaults to the Airprint driver for the device.

If you instead click "add printer or scanner" and select the printer from proceeding menu then it provides the ability to change the default driver to the HP Laserjet P1102w driver. I printed two consecutive multipage documents over the network without any delay. I will monitor the performance over the next several times I print and see if this is the true solution to the issue.

Intially though, it does appear that there is an Airprint driver issue either with the printer's handling of the protocol or something specific the Mac driver release. I haven't printed many items from my iPad or iPhone, so I can't really isolate it to a general Airprint driver issue or an Airprint support issue with this printer.

I moved the three seperate Macbooks in my house to the HP driver, each have printed multiple times tonight, and no delayed-filled printing was experienced.

I don't know if the default Airprint driver is at fault or HP's support for the Airprint protocol on P1102w is faulty, but I do feel confident that the driver switch solved this issue.

Yes, I imagine the pairing process for WPS does offer some security vulnerabilities potentially but it loads the same data into the device config as doing it manually. Also, Airport Utility 6.2 update added WPS printer pairing back into the interface. It had been missing since 5.6. It's officially supported by apple once again. Though I imagine the reason for the year or more exclusion was more due to the recoding effort with the 6.x interface change.

They may have one guy working on this thing seeing how their routers and utilities for the router are a low on the totem pole market for apple.

Doesn't Reaver require the access point to be in pairing mode to work? WPS has a pretty obvious security risk. I'm an IT guy myself and I pondered the security implication of the protocol time to time. Still, I don't believe access points such as AEBS publish the credentials to client requests unless the router is in the pairing mode.

If my assumption is correct, Reaver would require both good timing - catching somebody in an area pairing a device to their access point - and a little luck to be an effective exploit. Even with the SSID and AES-256 passphrase, they'd still have to pull a needle in the haystack MAC Address spoof out of thin air before getting any access to my AEBS.