I am not a web developer, and I do not know much about web application structures.
Recently, I ended up in Wt . This is a web framework written in C ++ (which is why I got into it), but what impressed me the most is the idea on which it is based.
Its API is different from any web structure I've ever heard of (CppCMS, Yii, Django, Pylons, Zope, Drupals, Java Servlets, Struts ...): a new application object is created for any user session, and it remains until the session ends (only at that moment the application object will be destroyed). This application object works like a desktop window: you put widgets in it (widgets such as forms, links, labels ...); when the user clicks on the link (when the HTTP server receives a new GET / POST request), the function is called on the object that is rigid to the user's session (in a good signal / slot way), which can delete / add / change widgets, thereby changing the page, which the user will see.
As I said, I’m not very good at web frameworks, I only develop desktop applications; perhaps for this reason I think this paradigm behind Wt is great.
I would like to know what are the pros and cons of this APIs in relation to others, and if other frameworks (also in other languages) exist based on the same concepts.
peoro source
share