Re: Re: Announcing Xaja, a PHP Reverse Ajax framework

I don't believe there is an equivalent in other languages. In Java, the closest match might be DWR for the Reverse Ajax approach, or maybe GWT for the "no Javascript" approach. I'm not completely sure, but I think nobody took exactly the same approach yet, because Xaja opens a large number of processes and connexions and most people believe that its architecture cannot adapt to thousands of users. For my part, since the vast majority of the applications I develop have less than 100 concurrent users, Xaja's architecture is perfect, and I hope it will spread in other frameworks and languages, because I find it really easier to develop applications with a events oriented architecture. David. Sancar Saran a écrit :

On Saturday 14 July 2007 15:01:13 David Négrier wrote: Hi I just watching your screen cast, it has very good ideas. I wonder does any other language has same kind of aproach. Later or sooner this kind of aproach become must in web business. Regards Sancar.

Indeed, Xaja relies on the keeping of an open connexion between the server and the browser. In fact, it uses, the Comet approach (which is a pain to implement in Javascript because the IE code and the Firefox code are completely different). (more information here: http://www.thecodingmachine.com/cmsDoc/xaja/trunk/architecture.html) The whole idea behind Xaja is to built a complete framework on top of the Comet-like javascript library that will enable the developer to write as few Javascript as possible. So, indeed, through the "XajaController" object, we are implementing a "data driven programming" library on top of the classical request/response HTTP protocol. Regarding performances: Indeed, since a connexion is kept open for each browser, this consumes a few connexions on the server (that's not a big problem). Each process also takes some memory. Xaja is still in an early stage of development and I haven't had the opportunity to run a full performance test, but basically, right now, I can tell that a simple applications takes 5 Mo of RAM per client. Which means that for 100 concurrent users, you need 500 Mo of RAM on your server. Now, the vast majority of the servers have less than 100 concurrent users, and at this early point in the development cycle of Xaja, I wouldn't recommend installing Xaja on a server that has more than 100 concurrent users! ;) Regards, David.