• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            woaidongmao

            文章均收錄自他人博客,但不喜標題前加-[轉貼],因其丑陋,見諒!~
            隨筆 - 1469, 文章 - 0, 評論 - 661, 引用 - 0
            數據加載中……

            無狀態類,有狀態類

             

            stated class, stateless class, 兩種類別,代表了一種思路

             

            在server端,不維護每個client的狀態,將會減少麻煩,是否需要引入無狀態思路呢?那么每個交互都是request<-->response模式

             

            有狀態模式,就是session維護模式,這還是非常常見的。

             

            參考

             

            Stateless or Stateful?


            Service objects will usually be stateless. Stateless service layers are highly scalable: They pose no replication
            issues and there is no need to allocate additional resources for every client. (Remember that one of
            the key motivations of a middle tier is to share resources between multiple clients.) It is also much easier
            for stateless service layers to support remote clients, if necessary.


            The traditional stateless service objects in J2EE applications are stateless session beans (SLSBs). I’ll use
            SLSBs as a starting point for discussion because they illustrate many of the basic concepts of stateless
            service objects, which predate EJB.


            A stateless service layer is one concession of object orientation that I find not too painful. Stateless service
            objects are semi-objects. Although they cannot expose state to callers, they can hold internal state
            and they can fully participate in inheritance relationships. If they are local, rather than remote, they can
            use true objects as parameters and return values.


            There are two main potential models for stateful service layers in J2EE: stateful session beans (SFSBs) and
            web tier session objects. If we don’t use stateful session beans, session data is usually held in Servlet API
            HttpSession objects. Holding session data in the web tier is usually more scalable than holding it in the
            EJB tier. (See Chapter 10 of Expert One-on-One J2EE Design and Development for detailed discussion of
            state replication issues.) “Thick” clients such as Swing applications will normally hold their own state.
            Because stateless service layers have proven their value in numerous technologies, including both J2EE
            and Microsoft platforms, we’ll focus on them in this book.

            If possible, design applications to use a stateless service layer. Hold state in the web
            tier, rather than in the business logic tier, if possible.

             

            對于EJB來講,Bean實例并非使用時創建,而是實現創建一個對象池,當client需要該bean中方法時,如果時無狀態的,容器會隨便指定一個空閑的給client使用,但是如果是有狀態的,容器必須記住上次是那個bean實例為這個client服務的,下次同一個client請求也必須由這個同一個實例來服務,不能換由其他的bean實例來服務

            posted on 2011-07-06 20:42 肥仔 閱讀(782) 評論(0)  編輯 收藏 引用 所屬分類: 編程思想

            久久综合亚洲色一区二区三区| 国产精品久久波多野结衣| 国产精品VIDEOSSEX久久发布 | 久久久久久综合网天天| 久久亚洲精品无码aⅴ大香| 精品伊人久久大线蕉色首页| 久久人人爽人人爽人人片AV不| 成人综合伊人五月婷久久| 岛国搬运www久久| 久久久久久久波多野结衣高潮| 91精品国产高清久久久久久io| 久久婷婷色综合一区二区| 99精品久久精品一区二区| 色综合色天天久久婷婷基地| 午夜精品久久久久久影视riav| 国产三级久久久精品麻豆三级 | 婷婷五月深深久久精品| 国产日韩久久免费影院| 日产精品久久久久久久性色| 久久有码中文字幕| 99久久99这里只有免费的精品| 中文字幕精品久久| 久久夜色精品国产亚洲| 久久99国内精品自在现线| 亚洲七七久久精品中文国产 | 欧美一区二区三区久久综| 看全色黄大色大片免费久久久| 久久99国产精品久久99果冻传媒| 久久久亚洲欧洲日产国码是AV| 久久www免费人成看国产片| 国产亚洲婷婷香蕉久久精品| 午夜精品久久久久久毛片| 久久久久av无码免费网| 亚洲精品美女久久久久99小说 | 午夜肉伦伦影院久久精品免费看国产一区二区三区 | 久久九九久精品国产| 亚洲天堂久久精品| 久久精品中文字幕久久| 99久久婷婷国产综合亚洲| 乱亲女H秽乱长久久久| 亚洲αv久久久噜噜噜噜噜|