Platinum Sponsors

SUN

ELCA

Gold Sponsors

AdNovum

Credit-Suisse

Silver Sponsors

SAP

SyBOR AG

Partners

Netcetera AG

JUGS - Java User Group Switzerland

Stadt Zürich Wirtschaftsförderung

cR Kommunikation

Eveni AG

LiSoG - Linux Solutions Group e.V.

Star Alliance

ICTnet

simsa

Creatronic Media Supply

Media Partners

Netzwoche

inside-it.ch

javamagazine

InfoWeek

IT Reseller

JavaSPECTRUM

APRESS

Nemanja Kostic

Nemanja Kostic

(1480) Avalanche framework - "coding-by-conventions" in Web development

Work-in-Progress

Tuesday, 2007-06-26, 17:30 - 18:10, Arena 6

Nemanja Kostic - Youngculture AG (speaker)

Topics

Download the presentation

Abstract

"Avalanche" framework is a Web framework used for extracting, 
presenting and manipulating data coming from any kind of data source - database, 
proprietary CMS's, filesystems, Webservices etc. 

Why is "Avalanche" different to other existing Web frameworks? 
"Avalanche" introduces a real coding-by-conventions concept in Web 
development. 
It is a component based framework, where each component is described with its 
corresponding object model. Components can depend on each other, meaning that 
action on one component can trigger actions of many other components on one HTML 
page - avalanche effect. "Avalanche" is fully Ajax based with reverse 
Ajax functionalities (server-push).
"Avalanche" differentiates from other existing frameworks in a way 
that it brings development one step closer to a data source while hiding all 
complexity of a Web development from HTML page customizers and system 
integrators.

Concept of "Avalanche" is best fitted to teams with a clear separation 
of development roles. Web designers, HTML prototypers, customizers and system 
integrators can work in parallel and can focus on their field of expertise 
without a need to learn some other technologies for fulfilling their tasks. 

Customizers and system integrators (who are creating data adapter to an existing 
data source) have an object model as a contract between them. They should not 
care about HTTP request/response parameters passing, action generation, Ajax 
logic etc. Data adapter developers should fill object model with data from the 
data source and HTML customizers should put those data in specific HTML slots. 
How data are actually generated and transfered, how actions are passed to 
server, how components communicate between each other etc., it is all a 
responsibility of the "Avalanche" framework.

"Avalanche" framework has proven its concept in a number of use cases 
and client's projects.