Anybody want an XMLHttpRequest

[Benson Margulies]

I've implemented an XMLHttpRequest for Rhino following
http://www.w3.org/TR/XMLHttpRequest/ as part of Apache CXF. I suppose that
the Rhino project could decide to pick it up and incorporate it directly.

[Attila Szegedi]

Hi,

thanks for the suggestion, but Rhino's scope doesn't include browser
environment. I believe your work would be of interest to people who
build browser environments around rhino, i.e. HtmlUnit/HttpUnit and
likes.

Attila.

> _______________________________________________
> dev-tech-js-engine-rhino mailing list
> dev-tech-js-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino

[Benson Margulies]

The W3C note seems to suggest that it's not implausible in non-browser
environment, but you're the guy in charge.

"Attila Szegedi" <szeg...@gmail.com> wrote in message
news:mailman.937.1195466529.352...@lists.mozilla.org...

[Attila Szegedi]

Well, to be precise, the W3C spec scopes it to a "user agent"
environment, and the spec itself requires a conforming user agent to
support a certain subset of functionality of the DOM3 Core and Events,
a subset of the Window Object 1.0 spec, and also have some intrinsic
HTTP support.

Rhino doesn't have any of these in itself, as it's just a core
JavaScript runtime.

The intent is to remain so, since JavaScript is today used in lot more
environments than HTTP user agents -- i.e. it's also the embedded
scripting language in the W3C CCXML specification, it is typically
found as an extension mechanism in XSLT transformers, and so forth.

Rhino can of course be used as a core component for a Java-based HTTP
user agent implementation. This is actually an often recurring theme
-- namely, a full HTTP user agent environment written in Java, with
Rhino providing JavaScript capabilities. That's why I mentioned
HttpUnit and HtmlUnit; they're both actually two examples (that I know
of) of this kind of a product.

Attila.