Re: [faces-dev] Partial Partial Updates

[Thomas Andraschko <tandraschko@xxxxxxxxxx>]

Hi,

i thought about it multiple times in the past.

The truth is that its probably not worth anymore to implement something in JSF.

Its a big effort to make components support something and we in PrimeFaces don't have the time and man-power to work on it. I don't need to say that we are the only big JSF component lib left.

Even for a DataTable, where it makes the most sense... How many rows do you have in a modern UI? Maybe 20 with paging? Dont think its worth it.

I though about reducing JSF AJAX response automatically with something like IceFaces did in the past.

I even initially created a prototype similar to IceFaces and Stefan made a real project for it https://www.beyondjava.net/introducing-babbagefaces-efficient-ajax-dirt-cheap.

Bet regards,

Thomas

Frank Cornelis via faces-dev <faces-dev@xxxxxxxxxxx> schrieb am So., 26. Jan. 2025, 10:29:

Hi,


Within Chapter 3 of the Enterprise JSF document, available via:
https://github.com/e-Contract/enterprise-jsf
I muse on how to apply different rendering techniques using JSF.

When looking at partial updates, right now it always happens at a component granularity level.
However, with a little tweaking the Faces runtime can be used to partially update selected sections of a component instead of the component as a whole.
The client-side Faces _javascript_ does not mind what it is actually updating, it just executes the received XML update instructions.
Under section 3.4 Partial Partial Updates, I implemented this idea using a custom PartialResponseWriter.
For some components, this has the potential to reduce the required update data set drastically.


Maybe the Faces API could support such "partial partial updates" directly?


Kind Regards,
Frank.



_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev