• <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)  編輯 收藏 引用 所屬分類: 編程思想

            亚洲国产二区三区久久| 精品久久一区二区| 欧美亚洲国产精品久久久久| yy6080久久| 精品无码久久久久久国产| 综合久久给合久久狠狠狠97色| 久久精品国产网红主播| 国内精品久久久久久中文字幕| 无码国内精品久久人妻麻豆按摩| 日韩精品久久无码中文字幕| 久久久久久久综合综合狠狠| 久久香蕉一级毛片| 嫩草影院久久国产精品| 伊人久久大香线蕉综合5g| 91精品国产综合久久久久久| 久久久久亚洲精品天堂| 久久精品亚洲精品国产欧美| 久久久久免费看成人影片| 伊人久久大香线蕉无码麻豆| 久久综合综合久久97色| 久久久老熟女一区二区三区| 超级碰碰碰碰97久久久久| 久久精品国产99国产精品| 麻豆精品久久久一区二区| 狠狠色婷婷久久综合频道日韩| 国产69精品久久久久9999APGF| 精品久久人人妻人人做精品| 国产精品久久久久影院色 | 久久久久AV综合网成人| 亚洲国产婷婷香蕉久久久久久| 国产精品午夜久久| 伊人色综合九久久天天蜜桃| 九九热久久免费视频| 国产—久久香蕉国产线看观看 | 色偷偷88888欧美精品久久久| 久久综合亚洲鲁鲁五月天| 国产精品99久久久精品无码| 97精品伊人久久大香线蕉| 99久久99久久精品国产片果冻| 久久精品国产99国产精品导航| 精品永久久福利一区二区|