Web Connection
Hitting the back button
Gravatar is a globally recognized avatar based on your email address. Hitting the back button
  Michael B
  All
  Sep 14, 2020 @ 03:43pm

Rick,

Can you suggest a non javascript solution to forcing a page refresh when a user hits their back button? Imagine a list of 'open' orders needing to be processed by a team of 20 users. Each order is at various stages of completion and it is possible that user 1 works on 'invoice.field2' while user 2 works on 'lineitems.field'. There is no need to lock the record, but there is the need to update the 'view' of the open orders so that user 3 does not start working on a step or process that is already at play.

I saw an example of this on a partners website and I asked their dev team how they do this? They said 'using sockets'. I know that WWWC has a socket class but I never played with it.

Do you have any demo's that might speak to any of what I am suggesting or you can provide any ideas on how to make a stateless page more stateful-like?

Gravatar is a globally recognized avatar based on your email address. re: Hitting the back button
  Rick Strahl
  Michael B
  Sep 14, 2020 @ 03:59pm

There isn't really a fool-proof way of doing this.

The closest thing is to generate all of your pages with an Expires: -1 HTTP header in the response which immediately invalidates the cache for the item. But - back button doesn't always play by those rules. Also you probably wouldn't want this for all pages - if you're on form with POST data you likely want to be able to go back and still have the form content in place instead of the back button giving you an empty page.

+++ Rick ---

© 1996-2020