Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsProvidersProvidersAlternative To Session Variables?Alternative To Session Variables?
Previous
 
Next
New Post
10/23/2012 10:10 AM
 

I saw your post, and was wondering if you had made any progress on a solution. It seems like a nice DNN Extension to provide for some functionality like what I see from the following link, which just describes a database-based approach to managing Session data. I do like your thoughts on tying this back to the aspnet membership functionality.

http://www.4guysfromrolla.com/webtech/041600-2.shtml#postadlink

 
New Post
1/1/2014 5:59 PM
 
The assumption that Session variables are bad for a server farm environment is wrong. It's trivial to configure ASP.Net's out-of-process state service. I've done this for my web farm. Since I'm depending on one database server, I setup the ASP.Net state service to run on the database server. Then I made a configuration change in the web.config to point to the database server's State service. IIS is not even required on the database server. Just make sure ASP.Net 4.5 or 3.5 is installed, then configure the state service to run through a registry tweak, setup the service to auto start, etc.
 
New Post
1/2/2014 8:16 AM
 

@Chuck Miller:

I am so sorry I never responded to your post...I never got a notification that someone replied to my thread until today (by Lucas Jans' post). No I never ended up getting a clean solution to this. I basically fudged it by placing code in each of my page's load method that updated a value in the DB with the current DateTime. Before each update, I would check the last stamp, and if the last stamp exceeded a certain "timeout" value (ie: equal to the DNN timeout value) I would assume the use logged out and back in. It works in "most" cases, as long as the person stayed in my module. If a user was bouncing around in other pages outside of my module...well...that could be an issue since the timestamp would not be updating properly. ::Shrugs:: Basically you have to jump through hoops right now in code. I have also used the DNN Caching methods, placing information in the cache with a relatively short TTL window, which helps insure that the data expires and gets removed.

@Lucas Jans:

I appreciate your input, however when you are developing a module, you do not have control over a customers server setup. If they setup their server farm to share Session States across servers, you are fine, if they didn't, you have a problem. I never said it wasn't possible to set up a farm to share session variables. As a developer, we can't assume environments would be set up correctly. Maybe the clients has a reason to not set it up, who knows. As such, I was trying to determine at the time, the best course of action to handle this. Saving the information to the DB with an expiration is the only method that I have found.


Ben Santiago, MCP Certified & A+ Certified
Programmer Analyst
(SQL, FoxPro, VB, VB.Net, Java, HTML, ASP, JSP, VBS, Cognos ReportNet)
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsProvidersProvidersAlternative To Session Variables?Alternative To Session Variables?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out