Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
6-28-2010 @ 5:06PM
Hih said...
"Gear-checking and /inspect requests in large raids will take much more time. Imagine the bottleneck presented of 10 requests every 5 seconds. That's 50 seconds of wait time for an entire raid check."
You mean... 10 seconds? 10 requests for the first 10 people. Wait 5 seconds. Another 10 requests for the next 10 people. Wait 5 seconds. 4 more requests for the other 4 people since I doubt you need to inspect yourself.
Reply
6-28-2010 @ 5:19PM
Arktic said...
I think he meant to say, "5 requests every 10 seconds." Either way, since the numbers were arbitrary, the point was still made.
6-28-2010 @ 5:20PM
Nvr said...
No.. it says 5 requests per 10 seconds. So 10 seconds for group one then 10 seconds for group 2 then 10 seconds for group 3 and so on and still 50 seconds because you would need 24 /inspections regardless of your own gear.
6-28-2010 @ 5:25PM
Mathew said...
Sorry, it's 40 seconds. My bad.
6-29-2010 @ 8:54AM
kingoomieiii said...
I assume in the future mods like GearScore, which already contain a P2P component, will use more aggressive timestamping and rely increasingly on slightly older information (not requesting a new inspect on a player if another gearscore user has an archived inspect on them less than a half-hour old, for example). Depending on how many guildies you have in the raid, you may find all the inspects have already been done for you when you roll over the players.