Not off the top of my head. Cisco's wireless site would probably be a good place. Bridges do not broadcast to wireless clients in the way an AP does. They talk to other bridges. That's it. They are used to link up wired sites. 10BaseT LAN in a building on a piece of property with a satellite office, either hundred of yards away or many miles. Each with self contained wired LAN's but the original building has a T3 and the sattelite office wants to get their hands on the connection. A point to point bridge setup works well. In that scenario with directional antennas on both sides. Or multiple satellite offices. Parent bridge at the Main site and children bridges at the remote sites. Omni at the parent site and directionals at the remote locations pointing back to the omni. It, in essence, makes the satellite offices part of the main offices network, but via wired clients. Now confusing this, you could connect a child bridge into a switch, and then plug AP's into that same switch for wireless connectivity within the satellite offices. Google search would probably get you some hits. Learned most of what I know on the job but I am sure there is literature out there that addresses this. The thing is, its semantics. WAP is a misnomor. Their Access Points. WAP is a wireless protocol used for phones and PDA's. Linksys started the whole WAP thing I guess and it has caught on with the budget Mfg's. It's irrelevant really and I have just accepted it but if you walked into a room with a bunch of guys that designed, installed and supported wireless LAN's and WAN's they'd laugh if you called an AP a "WAP" or a "bridge".