hehe ... thought that would tickle you.
I got the impression from the last post I answered (last post on page 1) that this was a commercial job in which time was an issue. I'm not at all averse to working this through with you. And yes, this is an interesting little problem with a valuable solution, if one is to be found. Perhaps even worthy of submission to the Joomla Devs for inclusion in future releases.
One question is do we need either? We are merely submitting a small amount of data to a data base and then displaying the results of that query.
I think so. Joomla very deliberately sends instructions to the browser at every turn in order to prevent local caching - and we specifically want to circumvent that as a first step in finding a solution to this problem.
I would try to keep it as stripped down and simple and base level as possible and use W3C standards and open source file formats. I do get the sense that this could be done this way, but like trying to get the correct answer you generally have to ask the right question...
I think you are correct to take this approach in the absence of any commercial pressures. Bear in mind though, that even the core Joomla project contains "transitional" as opposed to "strict" coding techniques in order to attempt a "best fit" between standards, functionality and ease of use for a wider community.
Clearly there are others that might want to use forms to query a database using PHP and would like it to be user friendly and go beyond simple HTML.
Throw in a bit more of a challenge and we add W3C standards and keeping Joomla upgradeable.
Increase the challenge a notch higher and you add in accessibility and strict valid code and CSS.
Now this is where we start getting our hands (tongues) tied. As a standalone solution, this couldn't be easier. We just send the header instructions to the browser to open up private caching and we have our solution. Within the Joomla framework, however, we have a multitude of existing constraints that we need to work around.
It may even be that we cannot achieve this within the confines of a Joomla Component. It may require core hacks in order to get around the 'no-cache' instructions sent by Joomla. I'm investigating the Output Override provisions of the 1.5 architecture as we speak in order to get my own personal project - DeepPockets - to work "correctly" within that architecture. I'm thinking that this may be a little further down the execution tree than we want to be for this problem though.
I will, no doubt, find the specific pieces of code we need to be working with. Whether or not we can override as opposed to overwrite these instructions will be another question.