Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Rendering compoenets on clients side / Performance issue  RSS feed

 
Ram Gokul
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • 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 ?
 
Chris Schalk
author
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
  • 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
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!