This content has been marked as final.
Show 5 replies
-
1. Re: Seam philosophy and scalability...
christian.bauer Sep 7, 2007 6:09 AM (in response to annbasso)we understand is stateful SBs don't scale that well
Maybe you should refresh that. Of course Websfear 1.0 doesn't scale.
http://in.relation.to/Bloggers/StatefulSessionBeansRock -
2. Re: Seam philosophy and scalability...
annbasso Sep 7, 2007 6:21 AM (in response to annbasso)Thanks for pointing to the blog. However, the blog just says that it scales well, doesn't actually try to prove or show that it is indeed a myth.
Of course, there has to be some state but shouldn't that be kept to a minimum? For example, in a standard shopping cart kind of application, you can have the cart items in the session. But to keep search results in the session? May be I am wrong, but it just seems too much.
The comments on the blogs also don't seem too encouraging. -
3. Re: Seam philosophy and scalability...
annbasso Sep 7, 2007 6:23 AM (in response to annbasso)"annbasso" wrote:
The comments on the blogs also don't seem too encouraging.
I meant, comments on Gavin's blog refered before. -
4. Re: Seam philosophy and scalability...
christian.bauer Sep 7, 2007 6:44 AM (in response to annbasso)So don't keep your search result in the middle tier and build it from the database/session/cookies/request parameters/second-level Hibernate cache on every request. It's all up to you.
-
5. Re: Seam philosophy and scalability...
pmuir Sep 7, 2007 1:14 PM (in response to annbasso)"annbasso" wrote:
I am evaluating Seam and trying to get the examples running. (Quite an exercise to get Seam 1.2.1 working on JBoss 4.2.1!!!...put this module in, remove that jar, tweak this tweak that...).
Seam 1.2.1 is NOT aimed at 4.2.1 so no wonder its a hard ride!(BTW, password rules for registering on this site suck big time!!! What is it a credit card processing company???)
Yes, we will have something better soon :)
As Christian says, Seam doesn't prohibit you from designing your app as you like. You'll notice different examples keep search results in different scopes (depending on your app the requirements change) e.g. booking in session, seamdiscs in the event scope.