Session vs GET parameters best practice

[José Moreira <jm...@e-terno.net>]

	Hello, i humbly confess that since my ASP/PHP times, not long ago,i've
been having problems understanding the 'best-practice' of 
Session vs GET parameters in CRUD's...

In my current application the practice i use is the following, for
editing a single PGSQL table:

 * a page displaying an result list with the records ( no paginator for
the time being), where a link like :

<detail> http://localhost:8081/editEvent.do?eventId=2

in each row points to a form where the user can instally manipulate the
data. In this page also there's a link like 

<delete> http://localhost:8081/deleteEvent.do?action=confirmDelete

pointing to an actions that redirects to an 'deleteConfirm.jsp'.

Because of the 'eventId' is being saved in the HTTPSession when the user
enters deleteEvent.do, the delete link doesnt have an &eventId=X ...

In the confirmPage i have 2 links refering to :

Really delete event? 

<Yes> http://localhost:8081/deleteEvent.do

<No> http://localhost:8081/editEvent.do

But because of editEvent.do 'needing' an ?eventId=2 for displaying the 

right record, the page throws an error, that means that 

deleteEvent.do?action=confirmDelete also needs ?eventId=2...

Resuming, it's a big mess, like this e-mail and my confused mind :)

Has anyone has thoughts for me?

thanks in advance ...


Ps.: I've read the manuals :)






---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org