title: Why do call interceptors in Play! Framework contain parameterized Http.Context?
body: <p>While writing a controller interceptor using the <code>@With</code> annotation, I figured that the <code>call</code> method of the associated <code>Action</code> contains a parameterized <code>Http.Context</code>. Since we can always refer to the current <code>Http.Context</code> via the <code>Http.Context.current()</code> call (which is execution context safe as well), why does Play!'s <code>call()</code> method have that as the parameter? Just wondering...am I missing something here?</p>