Asynchronous Web

  • What is asynchronous web?
    • server deliver state change to client, instead of client's state is not  consistent with server.
  • Ways to achieve
    • polling
      • sending request on a regular interval
      • pros
        • could have the effect of asynchornous web
      • cons
        • interval is hard to decide, may cause performance issue
        • if there is no update on the server, keep requesting is really not a good choice
        • polling is not a truly asynchronous mechanism
    • http streaming
      • One request, each response when server change
      • pros
      • cons
        • can't be deployed.
    • Long Pooling
      • Do not response until server change
      • pros
        • this is the ideal way to do this now
      • workflow
        • The initial blocking request is sent using XmlHttpRequest to initiate the long polling sequence.
        • Some state change in the application generates a response containing presentation updates.
        • The generated response is delivered to the client.
        • Client-side JavaScript handles the response and updates the presentation.
        • Loop back to the 0 state where another blocking request is generated.
  • Asynchronous Servlet
    • introduced in Servlet 3.0
    • Ajax push & Comet
  • Original Link for the topic: http://www.theserverside.com/tt/articles/article.tss?track=NL-461&ad=700978&l=WhatistheAsynchronousWeb&asrc=EM_NLN_6729006&uid=6526277

posted on 2009-07-12 12:52 simplelove 阅读(127) 评论(0)  编辑  收藏


只有注册用户登录后才能发表评论。
网站导航:
 

导航

<2009年7月>
日一二三四五六
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678

统计

常用链接

留言簿

随笔档案

搜索

最新评论

阅读排行榜

评论排行榜