Comments on: Client Server 2.0

By: IT-eye » Client-server 2.0 is taking off

IT-eye » Client-server 2.0 is taking off — Thu, 15 Jan 2009 15:01:33 +0000

[...] weeks ago i wrote a post suggesting the name client server 2.0 for browser applications which are completely generated in the browser using static javascript, [...]

By: IT-eye » Waarom renderen we de view laag eigenlijk nog op de server?

IT-eye » Waarom renderen we de view laag eigenlijk nog op de server? — Thu, 15 Jan 2009 14:56:15 +0000

[...] Client-Server 2.0 [...]

By: Andrej Koelewijn

Andrej Koelewijn — Mon, 08 Sep 2008 14:09:13 +0000

GWT is client-server 2.0 (i’ve updated the illustration) as it generates a javascript client which runs stateful in the browser. The javascript generates all the html needed to display the application. No application server is involved in producing the user interface. It’s just a static file server for the javascript files.

The only reason why GWT is not completely client-server 2.0 is that the communication with the server is not based on a standard like soap or rest. So i think the services used by the gwt application aren’t really reusable by other technologies. My experience with gwt is limited though, so i might be wrong here.

By: David C

David C — Mon, 08 Sep 2008 13:41:07 +0000

So how does a technology like GWT fit in there ?

By: Jan

Jan — Sat, 06 Sep 2008 09:26:58 +0000

No matter which client technology – Javascript/HTML/CSS, Flex, SilverLight, JavaFX – one thing is clear. We’re on the verge of creating more responsive, pleasant UI’s for our customers. They had to do without it for far too long.

Personally I like Flex better – for now – because of the more rich widgets and better/faster possibilities to talk to backend services. Much of Flex (and those backend technologies – like BlazeDS) have been open sourced and are (mostly) standards based also. On top of that it has a community which is growing steadily and I ’see’ developers flocking to it more and more.

I think we first need some consolidation on the Javascript frameworks side, as there are far too many in my view. Kind of reminds me of the abundance of web development frameworks that were/are out there. (Or are you writing ‘raw’ Javascript without the use of framework(s) )

By: Chris Neumueller

Chris Neumueller — Fri, 05 Sep 2008 18:14:45 +0000

Hi!

Actually, Oracle once worked on a Forms version nicknamed Cherokee. Rumours said that it had a standards-based HTML/CSS/JavaScript UI.

Chris