Difference between revisions of "Talk:Web Applications for AOLserver"
(AJAX discussion) |
|||
| Line 1: | Line 1: | ||
Before we can willy-nilly go off and implement one or more of these things, shouldn't there be some common model of application, user, role, etc, that should be defined so that there is at least the potential of some or all of the applications being able to co-exist? For example, to-do list, calendar, web-mail, if they all used a common model there would be the potential to tie them all in together (e.g. OSSWEB). | Before we can willy-nilly go off and implement one or more of these things, shouldn't there be some common model of application, user, role, etc, that should be defined so that there is at least the potential of some or all of the applications being able to co-exist? For example, to-do list, calendar, web-mail, if they all used a common model there would be the potential to tie them all in together (e.g. OSSWEB). | ||
| + | |||
| + | == AJAX discussion == | ||
| + | |||
| + | Has much been done in the area of AJAX implementations using AOLserver? Yes, it is another one of those buzz words full of promise, etc, and also full of drawbacks that people don't like to talk about. Yet it would be interesting to see what kind of performance AOLserver can do serving thousands of pages with thousands more AJAX requests. I would guess very good. The requests can probably be parsed by hand using ns_xml, but perhaps we could provide even simpler hooks for applications to use. | ||
Latest revision as of 17:44, 13 December 2005
Before we can willy-nilly go off and implement one or more of these things, shouldn't there be some common model of application, user, role, etc, that should be defined so that there is at least the potential of some or all of the applications being able to co-exist? For example, to-do list, calendar, web-mail, if they all used a common model there would be the potential to tie them all in together (e.g. OSSWEB).
AJAX discussion
Has much been done in the area of AJAX implementations using AOLserver? Yes, it is another one of those buzz words full of promise, etc, and also full of drawbacks that people don't like to talk about. Yet it would be interesting to see what kind of performance AOLserver can do serving thousands of pages with thousands more AJAX requests. I would guess very good. The requests can probably be parsed by hand using ns_xml, but perhaps we could provide even simpler hooks for applications to use.
