• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Rendering compoenets on clients side / Performance issue

 
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There was a thread in this forum some time back by developer who went from Struts to JSF and was having lot of performance issues because of the way compoenets are rendering .

To the authors , is the design of JSF such that components that are rendered on the client are downloaded page by page and hence pose a Performance problem . Has the authors faced any such issue ?
 
author
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ram Gokul:
There was a thread in this forum some time back by developer who went from Struts to JSF and was having lot of performance issues because of the way compoenets are rendering .

To the authors , is the design of JSF such that components that are rendered on the client are downloaded page by page and hence pose a Performance problem . Has the authors faced any such issue ?



Not sure I understand what you are trying to say. Actually they are "rendered from the server" not on the client (I think you meant this).

BTW, you can have components that really render on the client, but this means that the component renders JavaScript and then it takes over rendering - this is an advanced technique and not widely used.

So far, the only performance issues I've seen are with pages that have a unreasonably large (I mean really big) number of components on them - Of course stylistically you probably wouldn't want to have a page with an overly excessive amount of components on them anyway. Just common sense.

-Chris
 
You can't expect to wield supreme executive power just because
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic