> Sorry, I no longer work for the companies in question, so I can't give > exact details.
It doesn't have to be details about the work for the company itself. There seems to be a lot of factors in determining whether your application(s) ran with great performance (i.e. number of users, where you used WDDX, etc) and I'm curious as to how you gauge them. While I can see how someone would be able to write an application that uses WDDX better than someone else's app, I'm not sure how you determined that your app ran with great performace. In my understanding, there will always be overhead with WDDX because you have to serialize and deserialize. Can you also give some of your ideas on when someone should use WDDX, when not to, certain things to watch out for, etc? For myself, my favorite part about WDDX is being able to transfer data to Javascript easily. Beyond that, I haven't had _too_ much use for it. Ben Johnson ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
