Jade and Web 2.0 ?

[ConvertFromOldNGs]

by Alistair Mackay >> Fri, 21 Sep 2007 0:01:38 GMT

Has anyone used Jade in Web 2.0 stuff?
Or Called Jade using XMLHttpRequest?

[ConvertFromOldNGs]

by dcooper@jade.co.nz >> Fri, 21 Sep 2007 0:10:41 GMT

Yes - the customer portal we've implemented for EWS uses XMLHttpRequest from JavaScript to communicate with a JADE server-side via a Web Service Provider app.

Also, the "XML In JADE" white paper and schema here on the web site:

http://www.jadeworld.com/jade/whitepapers.htm#jadexml

has an example of doing this using an HTML <form> tag to send messages to a JADE Web Service Provider.

Dean.

[ConvertFromOldNGs]

by Alistair Mackay >> Mon, 24 Sep 2007 21:49:53 GMT

It looks like these kind of techniques are becoming more popular : some code snippets showing the Javascript connection to Jade would be useful to anyone wanting to experiment in this area.

[ConvertFromOldNGs]

by Brendan >> Fri, 21 Sep 2007 7:09:29 GMT

Yes, I've implemented an Ajax based client to replace the Jade Thin Client, though obviously both can co-exist. I used the dojo toolkit (see http://dojotoolkit.org) to implement the front end. This is a huge, comprehensive, open source JavaScript library which greatly simplifies writing Ajax and DHTML browser based front-ends. It works with the Jade server on Windows or Linux. The clients can be on virtually any platform and supports all the common browsers.

I used HTMLDocuments and used json for the message format, (see http://json.org) but I would suspect a WebService solution could be made to work just as well.

Cheers, Brendan

[ConvertFromOldNGs]

by John Munro >> Fri, 21 Sep 2007 13:50:24 GMT

Yes, we built a web application that communicates with the Jade db using web services, using xmlhttprequest

John

[ConvertFromOldNGs]

by Allistar >> Sat, 22 Sep 2007 2:19:07 GMT

Yes, I've helped implement an AJAX based system hung entirely off a Jade back end. Communications is not webservices but JHP (a Jade equivalent to PHP). The back end keeps track of the state of the front end and
an "engine" in the back end can modify the clients. The browser communicate to the back end (a flexible worker thread farm) using XMLHttpRequest.
--
A.

[ConvertFromOldNGs]

by Allistar >> Sat, 22 Sep 2007 2:20:29 GMT

P.S. Because the display on a browser is inherently object based, using Jade as a back end is a perfect match, giving power and flexibility.
--
A.