On 21 Dec (11:15), Gavin King wrote: > I suspect that many people would be tempted to vote for (2). > But is there really *that* much value in that for the users? > The interfaces themselves arent changing, so its a simple > search/replace followed be recompile.
Maybe this recommendation is a bit unpopular: Get rid of the name "Session"! I spent the last three days implementing lazy loading in a clean separated Three-Tier-Architecture and it's driving me crazy. Whenever I read the documentation, I also had this 100 milliseconds think time when I hit the word "Session" or "Transaction" until I realized that the statement was about the Hibernate thing, not about the _concepts_... Well, I have to manage two layers of Session Beans (stateful and stateless), a HttpSession containing a UserSession and some other stuff named similar. My code is clean, but the next developer looking at this stuff will have a hard time understanding why there's another "Session" in the Persistence Layer that uses UserSession to store its disconnected state and gets this one from the SessionContext of the stateless SessionBean Business Facade. And this was only have the system up from the bottom, there are some other "Sessions" in the top layer. Ok, it's not that serious, but I feel alot better already ;) -- Christian Bauer [EMAIL PROTECTED] ------------------------------------------------------- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
