1 2 Previous Next 20 Replies Latest reply on Nov 4, 2009 7:03 PM by Francisco Jose Peredo Noguez Go to original post
      • 15. Re: Seam 3: Flash scope and Conversation Scope
        Arbi Sookazian Master

        Think about a use case (scenario) where flash is useful. Now think you want to reutilize that code for that use case, but while an LRC is running. One possible example in during you 5 page wizard, you might need to pass some information that is generated in page 2, and relevant for page 3 but after that is no longer needed.

        So why not just use an LRC?  What is the big advantage with using flash scope just for 2 pages?  So those objects will be de-allocated faster in the heap?


        I really don't see the need to over-complicate things...

        • 16. Re: Seam 3: Flash scope and Conversation Scope
          Francisco Jose Peredo Noguez Master

          Arbi Sookazian wrote on Oct 05, 2009 21:59:


          Think about a use case (scenario) where flash is useful. Now think you want to reutilize that code for that use case, but while an LRC is running. One possible example in during you 5 page wizard, you might need to pass some information that is generated in page 2, and relevant for page 3 but after that is no longer needed.

          So why not just use an LRC?  What is the big advantage with using flash scope just for 2 pages?  So those objects will be de-allocated faster in the heap?


          Let me answer your question with a question:


          So why not just use Session Scope?  What is the big advantage with using LRC scope just for XXX pages? after all, all the behavior of LRC can be implemented using sessions (in fact, it is implemented that way in Seam, Conversations are nothing but an abstraction layer on top of sessions).


          Furthermore... why not code in assembler? why not use pucnh cards? after all, anthing that can be expressed in a high level language can also be represented in binary using puch cards. ;-)


          Simple answer: Because I want it to be easier.




          I really don't see the need to over-complicate things...


          Why create JPA if JDBC would suffice? why create any programming language if assembly would suffice? why use cars if walking would suffice... why create medicines if were are all going to die anyway? I really don't see the need to over-complicate things... ;-)

          • 17. Re: Seam 3: Flash scope and Conversation Scope
            Francisco Jose Peredo Noguez Master

            Ever wondered why the keyboard has around 100 keys when only 3 would suffice?


            The perfect keyboard for you ;-)

            • 18. Re: Seam 3: Flash scope and Conversation Scope
              Arbi Sookazian Master

              Let the rabbits wear the glasses, Reverand Maynard.  Amen.

              • 19. Re: Seam 3: Flash scope and Conversation Scope
                Shervin Asgari Master

                I can't really decide if this is useful or not. Because Arbi has a good point. This will kinda make things more complicated. While I also can see your point too Pedro.


                However, we must think about the end user and the newbies out there that already feels Seam is quite big, extensive and difficult to understand. Heck, it took me over 1 year of everyday use before I felt I got a hang of most of it.


                If we start introducing even more scopes that might be more confusing for the user. Anyways, thats my personal opinion. I take no sides on this issue.

                • 20. Re: Seam 3: Flash scope and Conversation Scope
                  Francisco Jose Peredo Noguez Master

                  Shervin Asgari wrote on Nov 04, 2009 10:23:


                  I can't really decide if this is useful or not. Because Arbi has a good point. This will kinda make things more complicated. While I also can see your point too Pedro.


                  Why more complicated? Temp conversations and flash are, from a behaviour POV almost the same thing, why not make it possible to explicitly control the promotability to long conversation (or even use more sensible nomenclature)



                  However, we must think about the end user and the newbies out there that already feels Seam is quite big, extensive and difficult to understand. Heck, it took me over 1 year of everyday use before I felt I got a hang of most of it.


                  And how do you think those newbies are going to feel when their already tested and working code goes crazy when they try to re-utilize it inside a long running conversation?. Keeping things inconsistently simple is not exactly a great advantage... I was also a newbie (maybe I am still?), and I did not like it when it happened to me!



                  If we start introducing even more scopes that might be more confusing for the user. Anyways, thats my personal opinion. I take no sides on this issue.


                  But flash/temp-conversations are already there, all I want is that Seam makes it easy for me to have the code using them be consistent and reusable.

                  1 2 Previous Next