ICEfaces vs. Richfaces

[asookazian]

Following if from Seam in Action:

Contention for the conversation isn’t seen when using ICEFaces since the ICEfaces framework automatically synchronizes requests from the same page to ensure that the server-side DOM remains uncorrupted.

What version of Richfaces will be able to do this as well so we don't have to worry about using eventsQueue and requestDelay, etc.??

[sergeysmirnov]

RichFaces doesnot use server-side DOM. So, the question is nonsensical in general.

[asookazian]

"SergeySmirnov" wrote:
RichFaces doesnot use server-side DOM. So, the question is nonsensical in general.

So are there going to be any mods done to alleviate the dreaded Seam error: ConversationEndedTimedOutOrWasProcessingAnotherRequest?

What design does Richfaces use if it's not server-side DOM??

[sergeysmirnov]

Read the Developers Guide.

[asookazian]

"SergeySmirnov" wrote:
RichFaces doesnot use server-side DOM. So, the question is nonsensical in general.

As nonsensical as it may appear be, it's even more absurd to a user to see that error (ConversationEndedTimedOutOrWasProcessingAnotherRequest) on the screen and it's definitely the most frustrating part of working with Richfaces as a Seam developer.

So Icefaces holds this significant advantage over Richfaces from a programmer's perspective (i.e. I won't have to manually consider and code for eventsQueue, requestDelays, etc. with Icefaces). If that situation simply cannot occur, that's great...