Why Vaadin handle push requests this way?

[Michele2 (Michele Preti)]

Hi all,

already in another thread (https://vaadin.com/it/forum#!/thread/3409292) i was surprised by the way Vaadin handles push.

Vaadin handles push request trough a PushHandler in which it call ServerRpcHandler().handleRpc(ui, reader, vaadinRequest);, this work, but completely skip the servlet (and it’s filters), giving two differents way (the servlet and the pushHandler).
This way enabling or disabling the push is a pain. If i code my application without push enabled and thus i can override servlet.service and filters, if i enable the push…i simply lose all my work.
Instead, if i use push, and manage to override (and right now this is not an easy task with the current architecture) the pushHandler i still have to do the same for the servlet, leading to duplicated code.

Would it not be more easy to reroute all request trough the servlet (using a
ReflectorServletProcessor
) ?

And, as Johannes Dahlström said:

many things change from request to request, and not all filter use cases work as expected when there’s only the single stored HTTP request available.

That’s right, but some filters might work.

So: why not unify these two way and use only the servlet?