wicket - Is REST a good choice for GUI web applications? -


GUI based web applications can be manufactured on a state-wide framework like a GUI component, wicket, or they can be constructed in a quiet, stateless way. Only with the GUI status on the customer can

RS appears in a technically correct manner because it leverages the full power of the HTTPS and leads to high scalable applications. But it comes at price. In many cases the complex GUI will require a Javascript application on the client. You have to stay on the same page and only need to reload the parts, if the customer should be maintained at the state. Or you have to use tricks with hidden iframes. Sometimes there are pseudo resources like Shopping Cart on the server, which enables a powerful design. You have to maintain the intermediate state of multi-step dialogs and so on ...

If I look around then there are very few reset GUI webpages. Is it because of historical reasons or in a general scenario a seamless design Is unproductive?

If I look around there are very few swelter GUI webapplications due to historical reasons Or is there an uncontrolled design in general scenarios?

My answer is subjective, but in my opinion, the two major obstacles obstruct calm development:

    Change
  1. - the way the site traditionally Designed, it is very different from that
  2. Challenge - Creating a pure reallst server API and a rich, strong client UI is not easy

Complex The GUI will need JavaScript applications in many cases on the client.

In my opinion, a complex, a rich customer-side experience requires something, regardless of server-side implementation, javascript in depth.

You have to be on the same page and only parts should be reloaded,

This is a complete page with traditional request / feedback Very different design from -to-full-page design Each design has its own business closed

  • Scales well : The information for the session is not stored in rare server memory for each user
  • Less requests / feedback data on the wire: do not send each page in full, do not send session ID or viewState S
  • Clear Clear Reusable URL: Provide a clean, decoded server API that UI:
  • Pure: Strict compliance for HTTP specification (no side effects, etc.)
  • Client Experience: Rich, more responsive with asynchronous transaction
  • However, as you mentioned, there are drawbacks in fat-client:

    • To develop complex JavaScript, It can be challenging to maintain and debug (using oo javascript etc.)
    • India needs
    • more client-side failure-handling logic is required
    • Frameworks and IDE tools are traditionally used Have become weak for client-side development, compared to server side (this is slowly getting better)

    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 -