Re: Ajax PEAR package

On 7/14/05, Alan Knowles <alan@akbkhome.com> wrote: > This seems rather rudimentary. > The PHP side is basically doing a cross between HTML_Javascript, SOAP > and XMLRPC. > I don't agree on this. HTML_Ajax is _an_ implementation of the remote scripting thru the use of XmlHttpRequest, strictly coulpled with JSON encoding. I never said it's the best implementation, I've not so much experience to say this :-)... On the other hand it's trivial that XML encoding is redundant and there's actually no need for this complex DOM encoding-decoding into a simple browser-server data communication. From a teorical point of view I sincerely that Josh has a really more deep knowledge of the 'ajax' topic than me... the point is that - and here starts my 2 cents opinion - the BEST implementation of a given functionality is not a real world concept but an utopia. For example I really don't see no need to encapsulate into a JS object a simple 3-line-of-codes function... this is a big concern for PHP because this kind of philosofy (complicate is better - just the opposite than KISS [1]) is a typical JAVA feature; according to me the PHP ajax implementation should marry the PHP philosofy: simple, fast, functional. Definitely I'm not sure we can wait more time to commit a PEAR ajax package, otherwise people can feel that rich GUI XHTML applications can only be driven by a rich ($$$) .NET backend or by complex flash objects. [1] http://en.wikipedia.org/wiki/KISS_principle