Re: counts the number of hit on a website containing many JSPs
Jean-Baptiste Nizet wrote:
The web has its rules and idioms, and web design is not the same as
Huh. Look athttp://bugs.sun.com/. The search form uses GET. And all the
links below the form look like internal hyperlinks to me.
Seehttp://bugs.sun.com/top25_bugs.do. All the bugs are accessible
through hyperlinks.
I didn't say Sun didn't use hyperlinks, I said they used these other
principles to good effect.
- Go tohttp://volume1.coreservlets.com/archive/Form-Processing/form-data/S=
ho...
- Submit the form (a simple post-base example form)
- Try refreshing the page using your browser's refresh button. On
Firefox, I get this ugly dialog box (translated from French): To display
this page, the information which has been transmitted by Firefox must be
resent. This will repeat any action (like a search or a shop order)
previously done.
No, it won't. Not if the web app is designed with idempotent
transactions, as of course, it should be. Repeating the action would
be a bug.
Don't use a bug as an argument against a technique. Argue against the
technique as it would be used with the bug fixed.
Hence the redirect-after-post pattern (aka
Post-Redirect-Get) used by good webapps.
Hence no need for that.
So you never had this dialog box I just showed you? And you never had
browser warnings about information which must be resubmitted to get to
the a page in your back history? You must be living in a parallel world,
or not use IE nor Firefox.
It's not a big issue. You hit "OK" and the screen refreshes. What's
the big deal?
Lew wrote:
Actually, I was wrong to limit it to POST. It's sessions that hold
that information.
Jean-Baptiste Nizet wrote:
I don't understand. If it's sessions that holds your precious
information, why would it be accessible only if you use POSTs? The
What part of "I was wrong" did you not understand?
session is tracked by cookies or by URL-rewriting, and both techniques
work with hyperlinks.
Not in the explicit sense of which I was speaking. Also, don't forget
that I am not against hyperlinks, just the indiscriminate use thereof
for internal navigation.
If all the products sold by ebay weren't accessible via simple URLs,
Ebay wouldn't be what it is.
If the search results of google weren't accessible by a simple URL,
Google wouldn't exist anymore.
If all the articles of ZDNet, Slashdot or whatever weren't accessible
via a simple URL, they wouldn't earn any money. Linking to the welcome
page of your webapp isn't sufficient.
Once again, I am not against all use of hyperlinks. Obviously you
have identified use cases where the web app opens up certain URLs. I
do not speak against that. I have stated many times in this thread
that web apps can open up certain URLs.
How is a link supposed to work if all your application accepts is POST
requests from buttons. Could you explain us? Hyperlinks generate GET
requests.
It would not be all the app accepts. Allow me to moderate my position
to say that such things must be done thoughtfully.
--
Lew