<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    Sealyu

    --- 博客已遷移至: http://www.sealyu.com/blog

      BlogJava :: 首頁 :: 新隨筆 :: 聯(lián)系 :: 聚合  :: 管理 ::
      618 隨筆 :: 87 文章 :: 225 評論 :: 0 Trackbacks

    Conversation timeout seems to be a commonly misunderstood Seam concept. I often see postings on the Seam forums claiming that the conversation-timeout doesn’t work! Well, actually it does, you simply have to understand the semantics.

    Configuring the conversation-timeout period can be accomplished through the following in your components.xml:

    <core:manager conversation-timeout="900000" />

    At first glance most developers relate conversation-timeout to session timeout, where any conversation will simply timeout after the configured conversation timeout period. As you will quickly notice during testing, this is not the case. To execute a quick experiment, try the following configuration in the components.xml of the seam-booking example:

    <core:manager conversation-timeout="60000" />

    Because the conversation-timeout is set in milliseconds, the above configuration sets the conversation-timeout to 1 minute. Now in the web.xml set the session timeout to 5 minutes:

    <session-config>
    <session-timeout>5</session-timeout>
    </session-config>

    Now in the destroy method of the HotelBookingAction add the following line:

    ...
    @Destroy @Remove
    public void destroy() {
    log.info("Destroying HotelBookingAction...");
    }
    ...

    This will log our message when the conversation ends and the HotelBookingAction is destroyed. Now deploy the seam-booking example to your local JBoss instance and start up a conversation. This can be accomplished by logging in, navigating to the hotels listing, and selecting a hotel for booking. At this point, wait for the 1 minute period… nothing happens. Now wait for another 4 minutes, the message is displayed. The conversation timed out along with the session.

    Foreground vs. Background Conversations

    So why didn’t our conversation timeout as configured? This is because the conversation-timeout only affects background conversations. The foreground conversation will only timeout when the session times out. Foreground, background, what? The foreground conversation is the conversation that the user last interacted with. A background conversation is any other conversation in the user’s session. Thus, in our previous scenario the foreground conversation timed out with the session as expected.

    Now lets try another approach. Perform the same steps as before to proceed to the booking screen. Now open a new window and perform the same steps. We now have a foreground conversation and a background conversation in progress. Again, wait 1 minute. Nothing happened. If you wait an additional 4 minutes, both conversations will timeout. So what is going on here, I thought we had a background conversation? We did, Seam simply checks the conversation timeout on each request. Thus, if I interact with the foreground conversation after 1 minute, the background conversation times out. Try it, perform the same steps, wait 1 minute and then click on the window of the foreground conversation and you will see the log message.

    This is very desirable behavior. Essentially when a user leaves his or her desk for a period of time and comes back, if the session is still active it would be desirable to maintain the state the user was previously in. This is the foreground conversation state. All other background conversation state is left to timeout after the configured conversation-timeout period which reduces overall memory consumption. This enables a developer to think less about memory usage and cleaning up state and more about developing business logic. That’s why we’re here right?

    Letting the user choose

    So you may be asking at this point why the conversation-timeout doesn’t use polling. As we said, you must interact with the foreground conversation to cause the background conversations to timeout after the conversation-timeout period. Imagine that the user had many windows open and leaves his or her desk. Based on which window the user clicks on when they return, that becomes the foreground conversation timing out any other background conversations. This gives the user a chance to resume whichever conversation he or she chooses, not the one the developer chooses.

    posted on 2010-04-20 00:36 seal 閱讀(461) 評論(0)  編輯  收藏 所屬分類: Seam
    主站蜘蛛池模板: 暖暖免费高清日本一区二区三区 | 亚洲免费在线视频观看| 国产成人综合亚洲亚洲国产第一页| 亚洲美国产亚洲AV| 女人毛片a级大学毛片免费| 国产精品亚洲一区二区麻豆| 大地资源在线观看免费高清| 亚洲人成网站看在线播放| 97在线观看永久免费视频| www.亚洲日本| 国产又大又黑又粗免费视频| 男女猛烈无遮掩视频免费软件| 亚洲国产综合无码一区二区二三区| 四虎影视久久久免费观看| 亚洲伊人久久精品影院| 精品亚洲永久免费精品| 精品亚洲成AV人在线观看| 91成人免费在线视频| 看亚洲a级一级毛片| 亚洲日本中文字幕天堂网| 在线看片免费人成视频播| 99久久亚洲精品无码毛片| 100部毛片免费全部播放完整| 亚洲一区二区三区高清不卡| 成年轻人网站色免费看| 人妖系列免费网站观看| 亚洲精品狼友在线播放| 成人免费大片免费观看网站| 在线观看国产一区亚洲bd| 国产亚洲精品免费视频播放| 99爱免费观看视频在线| 亚洲国产精品久久久久秋霞影院| 白白国产永久免费视频| 一级毛片免费不卡| 亚洲黄色中文字幕| 国产传媒在线观看视频免费观看| 精精国产www视频在线观看免费| 亚洲精品白色在线发布| 性做久久久久免费观看| 日韩电影免费在线观看中文字幕| 亚洲一级片在线观看|