| <<<--- |
Problems implementing distributed OO over HTTP |
--->>>
Page 12 |
Real problems:
- poor performance for easily programmed server interfaces (CGI)
- programming complexity using efficient programming server interfaces (NSAPI)
- dearth of toolkits for HTTP access, SSL, etc.
- lack of transaction control of server
- lack of 'web site' management tools
- lack of tools to scale applications over multiple machines
Supposed problems:
- HTTP is just used to server up HTML - true today, because there's not else
to see in browsers; the spec (and generally servers) are completely open-ended.
- HTTP requires a new connections for every request. No so in HTTP/1.1
and some 1.0 servers.
Patrick J. Mueller
(pmuellr@acm.org)
OOPSLA '96 Workshop on "Toward the integration of WWW and Distributed
Object Technology"