I'm a bit new to CourseWork, but one thing I found odd right off the bat was the use of the DTL. I do realize that CourseWork was first designed back when JSP wasn't a very good scripting language, but much of that has changed recently. Most of the stuff i've seen CourseWork doing with DTL could be done much easier with JSP.
Am i missing something? Is anyone out there interested in seeing it work with JSP rather than using DTLs?
... .joe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Coursework is essentially a CMS, although a highly constrained one. There is one aspect of its use of DTL's that is worth mentioning in the JSP context. It writes them. ie when anything in admin is updated the DTL for the couse is rewritten. This makes the processing a simple matter of personalising the DTL for the user in question.
In this respect the concept is simular to Velocity or other templating based frameworks. In reality it enables you to serve more users from the same box since most of the object and database calls dont happen.
However, I'm not 100% convinced a more traditional MVC or Model2 archetecture isnt better in this context ( < 25000 users).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm a bit new to CourseWork, but one thing I found odd right off the bat was the use of the DTL. I do realize that CourseWork was first designed back when JSP wasn't a very good scripting language, but much of that has changed recently. Most of the stuff i've seen CourseWork doing with DTL could be done much easier with JSP.
Am i missing something? Is anyone out there interested in seeing it work with JSP rather than using DTLs?
... .joe
Coursework is essentially a CMS, although a highly constrained one. There is one aspect of its use of DTL's that is worth mentioning in the JSP context. It writes them. ie when anything in admin is updated the DTL for the couse is rewritten. This makes the processing a simple matter of personalising the DTL for the user in question.
In this respect the concept is simular to Velocity or other templating based frameworks. In reality it enables you to serve more users from the same box since most of the object and database calls dont happen.
However, I'm not 100% convinced a more traditional MVC or Model2 archetecture isnt better in this context ( < 25000 users).