Duplicate announces

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Create an announce
2.Refresh the page
3.The navigator ask's you if you want to send the data once more
4.Chose yes

What is the expected output? What do you see instead?
Expected :
- The fisrt time : an announce has to be created
- The seconde time ("refresh time") : nothing
Current result : It creates an announces each time you refresh the page.

What version of the product are you using? On what operating system?
fsnet-0.7.0-SNAPSHOT
Ubuntu 10.04
Google Chrome

Please provide any additional information below.
Yes Fsnet does what it is suppose to do -> create an anounce, but it's better 
if there is a way to avoid to duplicate an announce by refreshing the page.

This is not a bug (or maybe it is), just a idea.

Original issue reported on code.google.com by tahar.ba...@gmail.com on 16 Feb 2011 at 7:05

[GoogleCodeExporter]

Same thing when you create a topic

Original comment by tahar.ba...@gmail.com on 16 Feb 2011 at 7:10

[GoogleCodeExporter]

You have the right to create an announce twice if you like, the way to avoid 
the refresh problem is your browser asking you if you want to resend the data.
As far as I am concerned this not a valid issue.

Original comment by stephane...@gmail.com on 17 Feb 2011 at 12:06

[GoogleCodeExporter]

This behavior appears simply because we use a "forward" instead of a "send 
redirect".

To fix this issue, simply redirect the user to the list of announces or to the 
created announce.

Original comment by mat.boni...@gmail.com on 17 Feb 2011 at 1:36

[GoogleCodeExporter]

Fix on r1678 by making a "send redirect" instead of a forward 

Original comment by mat.boni...@gmail.com on 17 Feb 2011 at 6:32

• Changed state: Fixed

[GoogleCodeExporter]

All the actions perform currently a forward. It might be wise to check for each 
one if a send redirect is better suited than a forward. 

Original comment by daniel.l...@gmail.com on 17 Feb 2011 at 7:55

[GoogleCodeExporter]

Last year we have started this work.

The rules we have used was : 
- Use send redirect with POST forms for CREATE/MODIFY/DELETE forms send by user 
and succesfully validated. (avoid "resend data" popup and prevent page refresh)
- Use forward with GET forms for READ action/forms. (permit copy/paste of the 
URL)
- Use forward with POST forms for CREATE/MODIFY/DELETE forms that have errors.

Original comment by mat.boni...@gmail.com on 18 Feb 2011 at 7:25