Should we store our data / BO in session


Author
Message
ChanKK
ChanKK
StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)StrataFrame User (414 reputation)
Group: Forum Members
Posts: 190, Visits: 1.3K
Hi
I have read some articles and post in asp.net forum. Everybody recommended NOT to store dataset / datatable in session as it will cause memory leak when user base goes large, would also reduce performance. As SF design is to store BO in session, does this design is good practice?

Beside, SF recommended to use SINGLE ApplicationBasePage for all page to reduce BO been created. If so, we always need to make sure the BO property in basepage use difference name even there are initialized with same BO type. What is the best practise on this? 

Currently we have ONE basePage for One form. If I want to follow SF apporach, anyway to refactor it without change all BO property name in all forms?

Thank you
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search