The system should always respond in a manner which causes the “least astonishment” to the user - i.e. a user should be able to predict what will happen when they do something and not be astonished by the result.
Screenflick features high performance screen capturing for smooth, fluid motion up to 60 fps. Screenflick can record any portion of the screen, simultaneously recording audio from internal or external microphones and the system audio.
I honestly don’t give a rat’s ass about architectural purity unless it achieves a pure purpose. The purpose of REST is to explain why you want to build it in a certain way given the Web’s own context. If that context doesn’t exactly match a new application’s context, then the goal of my dissertation is to teach people how to think about the problem in terms of trade-offs, not in terms of rigid repetition of what works for the Web.