which filter to use ?

 

>As I already write in this list, most browsers perform html page syntax 
>checks and corrections, but, in case of direct DOM manipulations this 
>stage is bypassed.
>Since, you can have two problems :
>1) html code, perfect rendered in html page can cause errors in 
>XMLHttpRequest parser, can be displayed incorrectly and even crash web 
>client.
>2) since html code processed in different ways, you can have unexpected 
>visual effects -  part of page can seems different after updated by AJAX.

>org.ajax4jsf.Filter use jTidy html correction engine and process both ( 
>initial and AJAX ) html responses in same way, and in most cases solve 
>both problems, even for complex page design. Use it optimal for 
>low-loaded sites, with complex html design. Initially, this filter was 
>developed for support Exadel Visual Components library and any internal 
>projects - we have dedicated web-designer, and need tool for convert art 
>to real world :-).
>On other hand, FastFilter only perform corrections for solve problem 1, 
>but more effective and fast ( up to 5-10 times on big pages ). But 
>developer must create more strict html code to avoid possible visual 
>effects. As usual, manual work provide most effective application, but 
>need more time to development.

>Padovan, Simone :
>> Hi,
>>  
>> Which filter do you suggest to use in a production environment ?
>> In the documentation and on the web page it's written to use the 
>> standard one: org.ajax4jsf.Filter
>> But in some posts on the forum I read that you suggest to use 
>> org.ajax4jsf.FastFilter.
>> Which one is better and when is better to use them ?
>> Thanks
>>  
>> Simone