Hello displaytag users,
We have displaytag pretty much working now, but I was curious about some of the details of the implementation:
1) After reading the forum, it seems that the recommended implementation for smaller data sets that still require pagination is setting the entire dataset to a session variable, using displaytag to present the data from the session scope. Can someone please confirm if that's correct?
One problem I see with the session is that it would get confused if a user opens two windows and tries to perform two different searches.. are there workarounds for this?
2) It appears that displaytag uses the GET method for "Next"/"Previous" pagination links. However if we are setting the results to the session, we don't need to pass the search parameters from page to page using GET, correct? Also is it possible to use POST instead? I saw one forum posting advising against it, but it did not go on to discuss the reasoning behind it.
Thanks to everyone for taking a look at my questions
Regards,
Dmitry
