• <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天天拍| 久久只这里是精品66| 日本五月天婷久久网站| 99999久久久久久亚洲| 国产精品久久久天天影视香蕉| 久久久久婷婷| 国内精品久久久久久久久电影网| 欧美丰满熟妇BBB久久久| 国产精品伊人久久伊人电影| 久久99热这里只有精品66| 久久成人精品视频| 久久国产色av免费看| 久久99精品久久久久久水蜜桃| 久久无码专区国产精品发布 | 久久天天躁夜夜躁狠狠躁2022| 久久亚洲私人国产精品| 一本久久a久久精品综合香蕉| 久久国产亚洲精品无码| 久久毛片一区二区| 久久99久久成人免费播放| 国产精品美女久久久| 99蜜桃臀久久久欧美精品网站| 精品国产一区二区三区久久蜜臀| 人妻精品久久久久中文字幕一冢本| 国产综合精品久久亚洲| 国产精品久久影院| 国产成人久久精品区一区二区| 97精品依人久久久大香线蕉97 | 久久午夜羞羞影院免费观看| 香蕉99久久国产综合精品宅男自| 久久96国产精品久久久| 精品国产一区二区三区久久久狼| 国内精品伊人久久久影院| 欧美久久久久久精选9999| 国产 亚洲 欧美 另类 久久| 免费国产99久久久香蕉| 久久久精品免费国产四虎| 久久久综合九色合综国产| 久久99国产精一区二区三区| 久久99精品国产自在现线小黄鸭|