Comments on: Concept: Four layers of web development

By: Mark Stewart

Mark Stewart — Tue, 12 May 2009 03:38:04 +0000

Nice bit of standards assessment! Behavior is also managed using CSS2. When CSS3 surfaces, the list of behaviors will grow. Also there are “tendencies” (I think they call them that, as they are intended to provoke certain, say, Javascript developments with native “unobtrusive” support). So perhaps Javascript belongs in a fifth catagory, with Ajax, Ruby, ASP, PHP, C and so on. We could unimaginatively call that web layer the Script layer. In the script layer, web development is set aside and platform development shuffles in. Javascript is an easily managed flirtation with server IT. However, it can be handily stressed that platform people are not fitting Javascript in browsers to web design, but rather to development of server technology. It’s a handy thing that the browser apps tend to maintain script cultures in their architecture so that web developers aka designers can resource script per rada nada. Fives a handful, but there you go!

By: Tom

Tom — Wed, 20 Aug 2008 13:34:34 +0000

That’s a really nice way of looking at and the diagram at the bottom really helps to illustrate your way of thinking. Although there is really nothing new here for the seasoned developed, it makes for a good read none the less.

By: M. Lowe

M. Lowe — Tue, 05 Dec 2006 19:47:55 +0000

Thank you, I am doing the same thing and just hadn’t put it to words as well as you have here. Good job.

By: Tim Bromhead

Tim Bromhead — Mon, 27 Nov 2006 10:40:03 +0000

Nice one, that is how I think too. You’ve explained it well.

By: Emil Stenström

Emil Stenström — Wed, 21 Jun 2006 21:41:45 +0000

Thanks, that’s much easier to read :)

By: martin

martin — Wed, 21 Jun 2006 20:11:10 +0000

@Emil: I said that I agree, ?? said that this was a useful article. I agree, the translators are terrable, probably has something to do with the verb being at the end instead of between the object and subject.

By: Emil Stenström

Emil Stenström — Wed, 21 Jun 2006 08:15:23 +0000

@??, martin: I’d like it if you used english on my blog, the korean to english translators are quite bad.

By: martin

martin — Wed, 21 Jun 2006 02:47:00 +0000

@ ??: ??? ??: ??

By: ??

?? — Wed, 21 Jun 2006 02:35:35 +0000

??? ????. ?????.

By: shavinder singh

shavinder singh — Mon, 12 Jun 2006 09:07:33 +0000

very insightful, honest, summative and quick-read stuff. i can’t even remember when was the last web-article i read without giving it up half-way. this in comparison was a breeze.

By: Henrik Feldt

Henrik Feldt — Sun, 11 Jun 2006 15:13:25 +0000

It would be more fun to read about server-side tiers and n-tier development where there really is something to discuss!

By: Emil Stenström

Emil Stenström — Wed, 07 Jun 2006 18:00:32 +0000

@Adedeji Olowe: Good comment. Hmm… I think that goes outside of this client side model. Even though I can imagine creating RSS-feeds from javascript ;)

A larger image of all the parts, both server-side and client-side would be nice, want to make one?

By: Adedeji Olowe

Adedeji Olowe — Wed, 07 Jun 2006 11:14:40 +0000

Shouldn’t be something called Interaction Layer? Where your website could interact with others (RSS, webservices, bla bla) which per see is not data or behaviour?

By: Emil Stenström

Emil Stenström — Tue, 06 Jun 2006 18:30:25 +0000

@Graham King: I’m not talking about code libraries here. This is just a way of thinking about what parts the client side is divided in. Javascript naturally belongs in the Behavoiur layer.

By: Graham King

Graham King — Tue, 06 Jun 2006 09:11:23 +0000

Emil – can you expand on the idea of a CSS abstraction layer? I’ve used the Behaviour.js library, which uses css selectors to add event handlers, but on a dynamic page this requires the DOM to be re-scanned after every change, which is a killer for performance.