Web portal architecture using a LOT of jQuery -


Some time ago I heard a very experienced web developer describing an ideal (architectural) architecture for a portal.
  • Web server (to use jQuery)
  • Talk to the application server)
  • Database and application layers made the total meaning and I have used the same paradigm in many projects, but I was astounded by the web server. It seemed as though all jQuery was going to be JSON or XML from the application server and was making a page in any way.

    It seems like a very calm idea. Unfortunately, I have never heard how it went. Is this sound a good design? Would you design a site like this? I'm sure they had a non-javascript tasting that would create stable HTML from the application server. Why not just put the whole site in non-javascript tastes?

    Note: I listened to this discussion and did not see any design drafts or anything, so I have some facts frightening.

    There is already one such application: Gmail - though it does not just use jQuery, but It's the same principle you define.


    Comments

    Popular posts from this blog

    sql - dynamically varied number of conditions in the 'where' statement using LINQ -

    asp.net mvc - Dynamically Generated Ajax.BeginForm -

    Debug on symbian -