"Domino is still a great product, but it is bordering on irrelevant in the Web 2.0 world."
If you think about web2 with ajax youll agree that most of the code execution is being taken away from the server and into the browser. After youll mostly have ajax calls to domino agents that either updates your model (data) or reads from it and throw xml to browser. If you can think better and start exploring the possibilitys of web2 with domino youll find pure RAD and flexibility. First, you can have an agent that acts as an universal view engine that you call with ajax and it sends xml data to browser. the browser beeing loaded with javascript you get sorts, filters, search, categorys, effects, pages, cache and all that in the purest web2 fashion. just one agent and some js and any view in any application gets web2. What youll benefit is the finest grained security out the box has domino data is "self-secured and user-aware" then youll have flexible data model wich is awesome and not matched by the ORM in java and neither by the active records like Rails, Cake, etc.. Some people might follow me but im scared most wont but still ill risk it: orm : domino maps document object directly to data, active record: its done without configuration and mapping can extend to html form for CRUD. That leaves thousand of possibilities :
1- domino renders data to html forms, then javascript acts as a transfomation layer for the few types of fields domino render improperly (dates, textarea, numbers), by scanning the form dxl with ajax these gets fixed once and for all. Now you get what : forms rendered correctly.
2-Next thing you need is flexible layout for xhtml or div id(ing) or nest(ing) that can be acheived by having a form for layouts and subforms for content. You get seperation of layout.
3-You can extract the domino action bar from the dom at browser side, reorganize it and integrate it anywhere you want. you get formula language actions or ls actions or js actions as plain dom li objects that can be flexed to the style you want but with hidden complexity.
4-You need an agent for ajax rpc to any ls library: that is easily dony because we have the "Evaluate and execute" fonction that can run a string as lotuscript or fomula from an agent in java or lotuscript. Short: you just need an agent that gets url params and build a string that is beeing executed. Note that security will properly apply because the agent runs as web user. What you get is the browser being given most libraries and tools via ajax calls to domino.
Performance has been a problem for domino with concurrent users but with ajax domino builds much lighter xml documents that gets xslized. You get awesome caching possiblities. That makes domino very scalable and rapid.
ok ill stop here but ill just come back to the point that web2 being mostly js, you only need from a server: security, flexibility of model and a complete api. Those thing domino offers unmatched in a standart way out the box. Domino is beeing given a new breed with web2 and it is awesome: sad the best developpers are working in j2ee frameworks and not on domino.
if you need a few hintwords: sarissa, dxl, xml, google xslt... domino data and security will bend to it unrestrictively.
Ed Malony said:
"Domino is still a great product, but it is bordering on irrelevant in the Web 2.0 world."
If you think about web2 with ajax youll agree that most of the code execution is being taken away from the server and into the browser. After youll mostly have ajax calls to domino agents that either updates your model (data) or reads from it and throw xml to browser. If you can think better and start exploring the possibilitys of web2 with domino youll find pure RAD and flexibility. First, you can have an agent that acts as an universal view engine that you call with ajax and it sends xml data to browser. the browser beeing loaded with javascript you get sorts, filters, search, categorys, effects, pages, cache and all that in the purest web2 fashion. just one agent and some js and any view in any application gets web2. What youll benefit is the finest grained security out the box has domino data is "self-secured and user-aware" then youll have flexible data model wich is awesome and not matched by the ORM in java and neither by the active records like Rails, Cake, etc.. Some people might follow me but im scared most wont but still ill risk it: orm : domino maps document object directly to data, active record: its done without configuration and mapping can extend to html form for CRUD. That leaves thousand of possibilities :
1- domino renders data to html forms, then javascript acts as a transfomation layer for the few types of fields domino render improperly (dates, textarea, numbers), by scanning the form dxl with ajax these gets fixed once and for all. Now you get what : forms rendered correctly.
2-Next thing you need is flexible layout for xhtml or div id(ing) or nest(ing) that can be acheived by having a form for layouts and subforms for content. You get seperation of layout.
3-You can extract the domino action bar from the dom at browser side, reorganize it and integrate it anywhere you want. you get formula language actions or ls actions or js actions as plain dom li objects that can be flexed to the style you want but with hidden complexity.
4-You need an agent for ajax rpc to any ls library: that is easily dony because we have the "Evaluate and execute" fonction that can run a string as lotuscript or fomula from an agent in java or lotuscript. Short: you just need an agent that gets url params and build a string that is beeing executed. Note that security will properly apply because the agent runs as web user. What you get is the browser being given most libraries and tools via ajax calls to domino.
Performance has been a problem for domino with concurrent users but with ajax domino builds much lighter xml documents that gets xslized. You get awesome caching possiblities. That makes domino very scalable and rapid.
ok ill stop here but ill just come back to the point that web2 being mostly js, you only need from a server: security, flexibility of model and a complete api. Those thing domino offers unmatched in a standart way out the box. Domino is beeing given a new breed with web2 and it is awesome: sad the best developpers are working in j2ee frameworks and not on domino.
if you need a few hintwords: sarissa, dxl, xml, google xslt... domino data and security will bend to it unrestrictively.
regards