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

            99精品国产99久久久久久97| 麻豆成人久久精品二区三区免费| 久久综合给久久狠狠97色| 久久精品无码专区免费青青| 性高湖久久久久久久久| 久久久久99精品成人片直播| 国产成人AV综合久久| 久久综合视频网站| 久久亚洲精品人成综合网| 久久亚洲精品视频| 免费观看成人久久网免费观看| 亚洲国产成人久久综合一| 久久综合视频网站| 久久99国产精品久久99| 欧美亚洲国产精品久久久久| 国产成人精品白浆久久69| 久久99精品久久久久久不卡| 久久国产亚洲高清观看| 亚洲v国产v天堂a无码久久| 99久久免费国产精品热| 一级女性全黄久久生活片免费 | 成人精品一区二区久久久| 性做久久久久久久久久久| 久久人爽人人爽人人片AV| 久久精品国产99国产精品| a高清免费毛片久久| 久久天天躁夜夜躁狠狠躁2022| 狠狠人妻久久久久久综合蜜桃| 久久久久AV综合网成人 | 久久精品免费网站网| 91久久婷婷国产综合精品青草| 久久久久亚洲AV无码观看| 亚洲国产天堂久久久久久| 国产综合免费精品久久久| 91久久成人免费| 66精品综合久久久久久久| 88久久精品无码一区二区毛片 | 久久偷看各类wc女厕嘘嘘| 狠狠色丁香久久婷婷综合图片| 午夜视频久久久久一区 | 伊人久久精品线影院|