Last post by Nowurtalkin:
*been absent awhile..
Thx for explanation. Yes, i think that part makes sense...and also that the simulator is a dev tool designed to check rendering & as such, i could be missing something, but it sounds then, that in this case & w/that purpose in mind, maybe it was a case of going outside the parameters of the simulators' purpose and/or capabilities, that is, in looking to it to prove/disprove whatever is/was the actual server issue (which might fall under the "wrong test" i surmised....or not). In other words, i was thinking that "page rendering" mightve been trumped by "page blockage"(?) i wonder, could the "emulator" (i think thats what its called?) have been any more helpful in this case. Academic question is all...
In any event, sounds like all good now, at least for those sites noted.
Originally posted by sahilbajaj23:
In this case, there appeared to be a server specific issue at the Opera Mini server processing client requests from India. Although that server must be using the same base code, it probably had some kind of extra 'setting' that was preventing certain sites from loading - if that makes sense.
*been absent awhile..
Thx for explanation. Yes, i think that part makes sense...and also that the simulator is a dev tool designed to check rendering & as such, i could be missing something, but it sounds then, that in this case & w/that purpose in mind, maybe it was a case of going outside the parameters of the simulators' purpose and/or capabilities, that is, in looking to it to prove/disprove whatever is/was the actual server issue (which might fall under the "wrong test" i surmised....or not). In other words, i was thinking that "page rendering" mightve been trumped by "page blockage"(?) i wonder, could the "emulator" (i think thats what its called?) have been any more helpful in this case. Academic question is all...
In any event, sounds like all good now, at least for those sites noted.