2013-06-10 We all know, the web is not state-less, as it should be. Currently REST (as far as I understood it) tries to remove the state, that was added later to the state-less web, again. But the real situation is even worse. Two examples. 1) The website of Deutsche Bahn (bahn.de). If you've found some train connection and you wait for too long, you aren't able to modifying that connection or altering the search parameters. You are not able to continue working from the state of the still open webpage because they cleared your state on the server. You have to start over again. Welcome back to the times when you went to the office desk and you weren't able to take a break while you were served. REST will solve that problem. (But I can't tell it often enough: REST is nothing new, its just a going back to were we came from.) 2) The website of the Focus magazin (focus.de). I was reading some article there and left the page open. Some time later, I found the following message in a virtual popup window on the page: HINWEIS: Sie waren einige Zeit inaktiv. Ihr zuletzt gelesener Artikel wurde hier für Sie gemerkt. (en: ``Notice: You were inactive for some time. Your last-read article was remembered for you.'') I had the choice between closing the popup and thus be put on the start page or klicking on a link that returned me to the page I've been on before. That's completely brain-dead. Why would I ever want that choice? Why would I ever want to be reminded that I was inactive for some time? That's something I'm obviously aware of. Why doesn't the webpage just do nothing? Actually, it's a webpage, it *should* do nothing. It should be static. http://marmaro.de/lue/ markus schnalke