Re: [w3c/gamepad] Vibrate feature for Gamepad (#19)

@luser Thanks for all your work on Gamepad to-date, it's so neat to see most browsers now supporting it.  

I have a concern with a Gamepad Vibration/Force Feedback API that the user's JavaScript could send too many change commands too quickly for some devices to make sense of.  If HTML5 does get Gamepad Vibration, could there be some sort of error code response to say "you're sending too much data, try again later"?  Maybe there could simply be a rule that only one command could be sent per axis per time slice?  

That might be too harsh, perhaps throttling the axis update data rate could be event-driven, but in any case, I would like an API that would perform reasonably well on most hardware and operating systems by holding the developer's hand a little and not letting him abuse the device.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/19#issuecomment-237051932