Jaxer Architecture Overview | Aptana

4 hypes hype it

How does Jaxer work? At a very high level:

1. Jaxer works closely with a web server to process and serve web content and respond to callback requests.
2. Jaxer reads HTML pages from the web server (Apache, Jetty, etc.) before they're sent to the browser, processes them, and returns the processed HTML to the web server, which forwards them to the browser — there are no proprietary XML formats or browser plug-ins needed, it's Ajax all the way.
3. Jaxer integrates the Mozilla engine — the industrial-strength engine that powers Firefox 3 — to provide rich, standards-based, well-tested parsing and APIs for HTML, CSS and JavaScript
4. To allow seamless calling of server-side JavaScript functions from the browser, Jaxer automatically injects a bit of JavaScript wrapper code into served pages. The actual server-side code remains securely on the server.
5. When you call a server-side JavaScript function from the browser, Jaxer wraps the function's name and arguments in a JSON string, sends them via an XMLHttpRequest back to Jaxer (via the web server), which unwraps the information, calls your server-side function, wraps the results back in JSON, and returns them to the browser, which unwraps them and passes them back as if the server-side function was running right in your browser.

comments Kommentare   addto Link hinzufügen  report als Spam markieren

T3N, das Magazin für Open Source und Webentwicklung.
Jahresabo inkl. Open-Source-Tasche nur 35 Euro.
Jetzt bestellen!

- Anzeige-