Showing posts with label browser. Show all posts
Showing posts with label browser. Show all posts

Sunday, February 20, 2011

Web based application problem

One thing the internet should do better is the consistency check of the data retrieved.
I know, there are suppose to be Network level check, but what im focusing on is the streamed/downloaded data.
Is it complete? or is it half way done.

One good example is downloading a huge file on the internet.
If its a zip file, its easy. Because we can check the zip file crc from the achieve application.

But isnt this suppose to be a web browser job?

There have been more and more Ajax base application out there, but yet,
i find that its not consistant in terms of opening the processed ajax output.
There are times when the internet got instable , and the browser thought the process is complete.
There are also time when the browser thought the javascript is downloaded complete, but its not.
This lead to instable output or undesired response from the server.
Most of the time, this could be fixed by refreshing, or clearing the cache and refresh.
But i think its best that there should be some kind of browser parity or consistancy check for completion, or dont render the output and output some kind of error message to the user.

Sunday, October 24, 2010

extJS on Chrome vs Firefox

The new modx 2 seems to be using extJS as their manager panel javascript ui.
Its a heavy framework, but proof to be quite handy.
But running on firefox is quite a problem.
As the longer you are using it, you will realise the memory slowly hike up, and you might be ending up having the entire browser slower and slower.
While in chrome, it works pretty smooth the entire time. So far havent notice any significant memory hiking. And performance changes have never been felt.
And comparing both chrome and firefox performance, chrome works faster in rendering the ui.

Version compared:
Firefox 3.6
Chrome 6.0