Another alternative to prototype is jquery, It's quite a bit smaller in
size than prototype, and in some way's it does things better than
prototype. I prefer prototype over jquery for large web applications,
and jquery over prototype for smaller ajax applications.
Also I like the jquery documentation better than prototype's, and jquery
is easier to learn.
Cheers,
Chad Minick
minglee wrote:
Thanks Dillon,
I have some problem with Firebug, because my environment is SuseLinux in
WMware, so I can't install Firebug online, but I did not find download item
for installation.
My javascript is quite simple the core is several functions handling
xmlHttp, the code is from a book named "Ajax and PHP Building Responsive Web
Applications" and can be downloaded from ajaxphp.packtpub.com. I am not
quite sure the error is javascript, because the error console of my browser
showed "uncaught exception: server error". After I clear all the cache (both
server side and client side), the problem still exits.
For prototype.js, there are struggles using it:
1. Too big. If plus codes I write, there should be a great size which will
bring limitations to many applications.
2. I am new to both prototype.js and ZF, if there is an error, I shall be
quite busy going between the two.
Regards
Dillon Woods wrote:
On 7/18/07, minglee <[EMAIL PROTECTED]> wrote:
However, when printing xmlHttp.responseText, it displayed content of my
another application's xmlHttp.responseText.
I think there must be something wrong with cache, but how should I do
with
the zend framework's cache in this case?
Are you using Zend_Cache inside your registerAction? If not, then I
suspect
the problem is with your javascript and not with the Zend Framework. Do
you
have an online example of the problem we could look at? I recommend using
the Prototype javascript library (http://prototypejs.org/) for making your
Ajax requests, it will take care of a lot of common javascript issues for
you. You might also want to get the Firebug extension for Firefox (
http://www.getfirebug.com/), it will show you exactly what is being
returned
to the browser from the server so you will easily be able to determine
where
the problem is.
Dillon
www.dewoods.com
