Requery or pass by GET/POST?

[vitalyb]

On a numerous occasions I have, on my site, a few pages sharing the same object that was loaded from the database.

For example, when user goes to ab article page, the page connects to the db and loads the article id, title, content etc.
Then from this page a user can vote for the article, but on the vote page I want to know the article name too.
Right now I am passing the article id by GET/POST and requering.

Question is, should I continue the way it is now or I should serilialize the object / send by GET/POST all the needed info?

What is the common thing to do in such case?

[LordShryku]

Well, is the query taking too much time/resources to requery on the vote page? And how much data are we talking about to send it via POST?

[vitalyb]

The query is hardly taking time - It is a simple "WHERE main_index = 4" styled query.

It can be pretty much info.. A few hundred chars. How much can GET/POST manage?

[LordShryku]

GET is fairly limited, and you don't want all that in the URL anyway. POST is user configurable in the php.ini. Default, it's set to 8 meg. I'm just wondering if you'll see any sort of performance gain from it. Dunno if it's worth changing.