3 ms·
having worked with JSF, I can safely say that me and server side rendering with peristent client connection to push updates are ... not friends. You have multi
by thecatspaw 8y ago
having worked with JSF, I can safely say that me and server side rendering with peristent client connection to push updates are ... not friends.
You have multiple scopes in the same document. You have the jsp scopes which gets rendered once, when the client requests the page, and the jsf scope which lives longer. Initially when rendering these scopes seem to share variables, but after the request is rendered, the jsp scope gets removed
- toolz 8y agoI promise you that your complains are with the abstractions chosen and implementation and not the concept. Texas doesn't have any of the issues you're talking about. You don't even worry about the data that populates the view. You simply write view code like any other templating engine that knows how to render itself and when data changes you send a small message to a process that handles updating the client and texas handles all the logic for efficiently updating its client.