7 Replies Latest reply on Feb 17, 2008 1:25 PM by pmuir

    Booking ScopeType.SESSION

    vicky123

      Hi All,
      I am very new to seam. Can any one tell me why searchHotel result of booking application is
      in SESSION context? Does not it effect the server memory when multiple users are logged in?
      Is there any other way of doing it or seam handles it effectively?

      Can any one throw some light on it?

      -Vivek

        • 1. Re: Booking ScopeType.SESSION
          dhinojosa

          Great question.

          • 2. Re: Booking ScopeType.SESSION
            vicky123

             

            Great question.

            I don't know what does this mean but still I dont know the answer of my question.

            Can any one tell me why is it like that?

            -Vivek

            • 3. Re: Booking ScopeType.SESSION
              gus888

              I think that it is just for demo, and the same case happens in seam-bay AuctionSearchAction.java. For enterprise project, I remember that pete.muir ever recommended to use EVENT plus page param in this forum.

              • 4. Re: Booking ScopeType.SESSION
                pmuir

                It depends on your use case. In the booking app, we wanted the search results to be remembered while the user is logged in.

                Yes, it's uses memory, but doing the search every time would consume cpu - you need to make this design choice when you write your app.

                • 5. Re: Booking ScopeType.SESSION
                  dhinojosa

                   

                  I don't know what does this mean but still I dont know the answer of my question.

                  Can any one tell me why is it like that?


                  I said that because, I don't think anyone can really answer that except the stewards of Seam. All other answers will be pure speculation. I was just supporting your question.

                  I am beginning to think that there should be a warning not to put any SFSB as Session scope or higher due to memory consumption.


                  • 6. Re: Booking ScopeType.SESSION
                    vicky123

                     

                    I said that because, I don't think anyone can really answer that except the stewards of Seam. All other answers will be pure speculation. I was just supporting your question.

                    I am beginning to think that there should be a warning not to put any SFSB as Session scope or higher due to memory consumption.


                    I am sorry I misunderstood.

                    Anyways my use case was not allowing me to use SESSION context in. I have done it using param.

                    Thanks a lot all.

                    -Vivek

                    • 7. Re: Booking ScopeType.SESSION
                      pmuir

                      Dan, we outline why the session scope is a problem in the docs intro and every presentation we do :)