Subject:
|
Re: Uh Oh... (was Traffic Error )
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Tue, 20 Apr 1999 16:16:43 GMT
|
Viewed:
|
1147 times
|
| |
|
|
In lugnet.admin.general, edboxer@aol.com (Ed Jones) writes:
> Just out of curiosity, was Mr. McDonald posting from the webpage instead
> of newsgroups.
Yup! Exactly, that's what we're looking into...
> The reason I ask is....
>
> When posting/replying from the web page (which I am doing now), upon
> clicking the Post Message button, you receive a confirmation message
> screen. But, when you click on the browser <Back> button, it takes you
> to the reply that you wrote and just sent. Is it possible that Mr.
> McDonald did this and thought that he had written the reply but not
> sent the reply?
>
> Of course this would be dependant on his keeping his web browser open
> the entire time. He could have visited other sites and by hitting the
> <Back> button suddenly came upon the message that he thought he had sent.
That was my thought. It's the only logical explanation, given the data in
the webserver logs.
The bummer of it is: Although it would be easy enough to embed a unique key
in a hidden form field on the /news/post/ page to ensure that the same form
couldn't be used twice to post the same message twice, that sort of thing
would prevent a form from being used twice for legitimate reasons -- i.e.,
posting two different messages to the same group. If a unique key were
embedded in the form (generated on-the-fly when the form page was loaded), a
user would then have to reload the form page for subsequent posts, which is
not only unintuitive but would require explanation on the page, which
complicates the system somewhat unnecessarily and makes the human work for
the computer rather than vice-versa.
Another workaround would be to do some sort of checksum analysis on the
content to make sure it wasn't identical to previously posted content, but
it would have to take into account things like adding a missing sentence or
blank line. And if the content was similar but different, would it
automatically go and delete the previous article?
Probably best all around would be some kind of warning system to the user.
If the server suspected that the Post Message button was clicked twice, it
could put up a big shiny red box asking the user whether he/she *really*
wanted to proceed.
--Todd
|
|
Message has 2 Replies:
 | | Re: Uh Oh... (was Traffic Error )
|
| (...) Please, call me Tom. I've been known to call you Ed when you're not looking :) (...) I just thought of another logical possibility that eluded me last night: I probly had opened another browser window when I was typing my message to be able to (...) (26 years ago, 20-Apr-99, to lugnet.admin.general)
| | | Re: Uh Oh... (was Traffic Error )
|
| (...) [major snip] (...) Another possibility would to add a link back to the Discussion Group on the Message Confirmation Screen saying something like "Return to Lugnet Announce". That would eliminate the necessity of hitting the back button (and (...) (26 years ago, 20-Apr-99, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Uh Oh... (was Traffic Error )
|
| (...) Just out of curiosity, was Mr. McDonald posting from the webpage instead of newsgroups. The reason I ask is.... When posting/replying from the web page (which I am doing now), upon clicking the Post Message button, you receive a confirmation (...) (26 years ago, 20-Apr-99, to lugnet.admin.general)
|
27 Messages in This Thread:
 
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
