Comments on: Two kinds of AJAX: HTML++ vs Client / SOA

By: Leading the Enterprise Ajax Revolution » Blog Archive » Client/SOA and Server-side proxy

Wed, 28 Jun 2006 18:47:15 +0000

[...] This is one approach to combining AJAX-based applications with a service oriented architecture. It implies web service invocations from a browser and has gotten quite a bit of coverage, including a mention on Ajaxian.com [...]

By: Ajaxian » S3 Javascript Bindings

Ajaxian » S3 Javascript Bindings — Mon, 24 Apr 2006 10:39:30 +0000

[...] The service is ideal for Client-SOA apps, where the browser runs the entire UI and makes REST or RPC calls to the server, which responds with raw data. The app itself could presumably load from another URL, your local hard drive, a bookmarklet, or a plugin/extension/GM script (with varying levels of security risk involved). [...]

By: Ajaxian » Screencast: Data Grid as Example of Rich Ajax

Ajaxian » Screencast: Data Grid as Example of Rich Ajax — Tue, 21 Feb 2006 01:26:13 +0000

[...] The other day, we linked to Harry Fuecks’ distinction between HTML++ (regular web app with a bit of Ajax thrown in) and Client/SOA (full-blown rich Ajax app). As I’d been discussing a similar idea (Ajax-Lite versus Ajax-Deluxe), I posted a followup. [...]

By: pwb

pwb — Fri, 17 Feb 2006 01:09:02 +0000

I don’t want to do it server side. That’s the point. For crying out loud.

By: Mikael Bergkvist

Mikael Bergkvist — Thu, 16 Feb 2006 10:50:03 +0000

If you need to pull data/xml from another domain, do it serverside and then feed it to the page using Ajax, for crying out loud..

By: pwb

pwb — Thu, 16 Feb 2006 04:26:19 +0000

GenInterface nailed this several years ago but got scooped up by Tibco. I think their stuff now resides here:
http://www.tibco.com/software/business_optimization/gi_resource_center.jsp

They enable very robust browser-based, single window interfaces. And they were able to pull down large blocks of data for local manipulation like sorting and filtering.