Hi Ronald, Thanks a lot for your advice, yes, it is very useful to check out server log. For prototype.js and script.acoul.us, I had tried on phpCake, yes, very convenient and easy. But for ZF, there is no such automation. Talking about broadband, yes, you're right in most cases, but some crowded situations should be taken into account. 1.Gateways: especially for international browsing, gateways among ISPs are limited. 2. Peak hours: if the web is busy, or the visitor's traffic is busy, speed will be reduced a lot. Both cable modem and ADSL have such problems, and these have most family users. 3. Other elements: 200k is not big, but on a homepage, there are other elements, including, images, links.
Regards, Calvin Ronald Becher wrote: > > Hi minglee, > > I daresay, you should check the server's error log for more information. > ;) > Or using firebug, it really is a great piece of software and i'm happy > with it using it in every day's work (in fact i can't get it, how i did > without it ...) > > Regarding prototype: > An actual version of prototype.js and script.acoul.us is 235 kB. > 1.) I don't think, that's such a large quantity ... not in times of > broadband internet and the average image being bigger than that. > 2.) You forget, that the javascript files are being cached by the browser. > I don't see a problem there. > Alternatively I just couldn't understand your sentence ;) ... About every > two Rails-Application (for instance) utilizes prototype.js and they > haven't found 200 kB to be a "great size" > 3.) Quoting one of my favourite sentences from "The Pragmatic Programmer": > "select isn't broken" > It's very unlikely, that you found a bug in prototype.js with a simple > xmlRequest-function .... > > Greetings > Ronald > > > minglee wrote: >> >> Thanks Dillon, >> (..) >> 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. > -- View this message in context: http://www.nabble.com/Apply-ajax-in-Zend-Framework-tf4101038s16154.html#a11704701 Sent from the Zend Framework mailing list archive at Nabble.com.
