Good luck with that. HTTP is not a protocol where the server is in control. In fact, for each page request/submit action, the client effectively logs in, does a single task, then logs out before the resulting new page is rendered.
No mechanism exists in any known HTTP client application that notifies the server when a request is made either to a different server or even to a different location within a previously-referenced webapp. No standard protocol is defined that would facilitate such behavior. And, in fact, since the same client is often commanding multiple browser windows, each of which potentially communicates with a different server, it would be difficult to conceive of a way of determining when notification is required. In fact, since a single web page often cascades into multiple requests to different servers (such as Google AdWords, ad.doubleclick.net, and so forth), the concept is practically meaningless.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Aug 03, 2012
Okay, thanks a lot.
I'll solve my Problem with a ViewScoped Bean then... not perfect but will work.