>There's nothing to rework if you choose not to. The only thing you would
>need to change in an existing HTML 4 application is the pages inside the
>frames and leave the frameset page alone.
"There's nothing to rework ... The only thing you would need to change ..." Contradictory. Which is it?
>"What's wrong with that?"
On what you say, to enhance the pages and keep them standards-compliant, I have to re-work them. That's an abuse of standards, which should not break valid working code providing simpler & neater solutions than the enhancements can.
Especially when the motives for breaking the previously valid code are unreasonable.
> Is the "can be widened" essential to your use case?
> ... http://chudosok.detyabozhye.com
Nothing near the functionality I am talking about. Think http://msdn.microsoft.com/en-us/library ... 90%29.aspx
>I also gather you're not very proficient with server-side technology.
As the Apache SSI page says, "SSI is certainly not a replacement for ... other technologies used for generating dynamic web pages..."
These are database-driven PHP pages.
And new standards ought not to require that working code be re-architected in order to remain standards-compliant.
>There are ways to do this without any server-side scripting, but
> server-side scripting is very helpful in this, as well many other things.
> Plus, there are far more technologies than ASP, many of which are
> arguably simpler to use to do many things including help emulate
with 10% of the code or less and no dependence on the underlying OS.
If you can provide similarly efficient examples of a non-ASP replacement for the use of frames I am talking about, your argument amounts to "to be standards-compliant, rewrite it". That is unacceptable.
Absent such examples, I have to conclude that HTML5 makes the functionality I depend on impossible without the overhead of an ASP solution or something similar. Doubly unacceptable.
> To be honest though, I doubt you will make anyone change their mind.