Difference between revisions of "Technical problems with the Web"
From Nick Jenkins
(convert from HTML) |
m (+cats) |
||
| Line 15: | Line 15: | ||
* Problem: frames require multiple HTML pages, instead of one HTML page that includes everything needed to show the page. | * Problem: frames require multiple HTML pages, instead of one HTML page that includes everything needed to show the page. | ||
* Result: unnecessarily harder to write pages that would benefit from frames. | * Result: unnecessarily harder to write pages that would benefit from frames. | ||
| + | |||
| + | [[Category:Software Development]] | ||
| + | [[Category:Computers]] | ||
Revision as of 04:21, 9 February 2006
Javascript as a browser technology
- Problem: JavaScript is very useful, but it can be a security hole, and it can turned off, and each browser has a different-enough implementation of JavaScript to be very annoying.
- Result: JavaScript is therefore much less useful and less liked than it could be.
- Possible partial solutions: XForms? Standards compliance?
HTTPS incompatible with virtual hosting
- Problem: cannot have multiple HTTPS virtual hosts on one IP address on the standard HTTPS port.
- Result: hard to host SSL sites.
- Solution: need to change the HTTPS protocol to support virtual hosting.
Design of Frames sucks
- Problem: frames require multiple HTML pages, instead of one HTML page that includes everything needed to show the page.
- Result: unnecessarily harder to write pages that would benefit from frames.
