TDDD27 Advanced Web Programming

Technological Requirements

Frameworks

Server-side framework: Your web application should be built using a server-side framework. Examples of server side framworks include Django, Node.js, Ruby on Rails, TurboGears, Codegniter, ASP.Net MVC, Google App Engine for GWT projects. There are many more and you will save a lot of time searching for a framework that suits you and your project.

Client-side framework: Your web application should also be built using a client-side Javascript framework, such as JQuery, Dojo Toolkit, or Rafael, Google Web Toolkit.

Remember: Don't use designers like in visual Studio to create your client-side UI or use UI-component genreated on the server. You should send only data from the server and inser or change the GUI on the clinet-side. Working with a system like Derby.js or Meteor.js - which in the client code handles the server side code is also ok (combined with a Node.js backend that works like a persistant storage or BAAS - backend as a service).

Data and user management

Data managment:(A) Traditional ER database like MySQL - use an ORM (object-relational mapping) such as LINQ/Entitiy Framework in .Net C# or Active Records, avaliable in most frameworks. (B) NoSQL storage - use that which works.

Account management: Use what provided or use an external systems such as oAuth, Open Id or Open Social, to login and authenticate users. What you cannot do, unless specifically granted that permission, is to build your own system.

Also, for really great web-related experimental ideas from students that really know what they're doing, I'm all for discussing alternative ideas and letting you create a design totally outside the box for something spectacular, even if you end up failing dramatically but learning a lot. It still has to be web, naturally.

Page responsible: Erik Berglund
Last updated: 2012-03-01