I suggest you ...

process tweets server-side rather than client

sometimes the script processing becomes heavy that the page is unresponsive for some time. You might wanna think about how to do this...will be glad to help though

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    deostrolldeostroll shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • deostrolldeostroll commented  · 

        I don't agree when you say there isn't much processing to be done.

        Take for e.g a simple tweet. It might contain urls; some of these url might be shortened via services like bit.ly. We'd have to fetch this information via server-side http requests again. So you can image the load this might have on the server. The best way to do this is via some threads, but you'd have to carefully plan it out.

        Btw, even on chrome running on windows, I got a kill page dialog box. It makes the browser irresponsive

      • HarshadAdminHarshad (Admin, tDash.org) commented  · 

        Thanks @deostroll for the suggestion and offer to help.

        On first look, there isn't much processing done on the client side which can be moved to the server side. Do you have anything specific in mind?

        And btw, which browser are you using? On Google Chrome and Apple Safari the application is quite snappy. On Firefox 3.x, I will conceded it does seem laggy. Hopefully, Firefox 4 will level the field soon.

      Feedback and Knowledge Base