Re: Share Single Session between different .net Solutions

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

If you have to maintain common "session", you will have to store data
somewhere.
IMO you can write somekind of session wrapper that will simulate ASP.NET
session object.
Doing so will result in small code change. Also you can define BasePage
class, and inherit all forms from it.
This BasePage will contain Session property that will point to you session
wrapper.

--
Vadym Stetsyak aka Vadmyst
http://vadmyst.blogspot.com

"Rommellion" <rrabie@xxxxxxxxx> wrote in message
news:1135675033.928640.239020@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> We have 5 to 6 projects .net running on production, in which each one
> has its own virtual direstory, however we need to add up two more and
> link them all together so they can share same single session state. we
> are doing this for some Authentication and Role identification
> purposes.
> We dont want to use any Db like storing session in SQL Server or
> whatever, also we dont need to use niether encryption nor passing
> parameters, because we will have lot of heck in changing the code in
> all of our projects.
> I tried to develop a simple prototype in which two different
> application one of them stores value in a session and the other try to
> read from the session, also with use of another page, but simply it
> failed.
> I looked over the internet for a real solution but nothing i can depend
> on so far.
>
> Any Clues??
> Thx
>


.

Relevant Pages

  • Re: controls & Session
    ... There is a relatively large amount of data - it is for a sorting and paging functionality of some data, so I did not want to use ViewState. ... I had thought about simply ensuring that each control uses some "custom" and unique naming convention for Session data - I had just hoped I would not have to resort to changing the controls' code, as they are "working components" which I didn't really want to touch. ... - Generally web pages have to recreate their datasets each time a page is written out however you can store data in the session cache with a reasonable timeout period and then recreate the data only when necessary. ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: controls & Session
    ... There is a relatively large amount of data - it is for a sorting and paging ... the Session is probably a good idea. ... - ASP.NET pages have a ViewState, you can use that to store data in. ... does a control know when it is no longer being shown? ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: controls & Session
    ... You can use more creative session variables names that indicate which page they are storing data for but that will probably only introduce different problems and bog down your session/server. ... Generally web pages have to recreate their datasets each time a page is written out however you can store data in the session cache with a reasonable timeout period and then recreate the data only when necessary. ... Peter Kirk wrote: ... does a control know when it is no longer being shown? ...
    (microsoft.public.dotnet.framework.aspnet.webcontrols)
  • Re: ASP.NET viewstate question
    ... ViewState only applies for the current page. ... values between postback. ... You could use Session to store data related to the whole session. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Passing a variable between pages or scripts
    ... individually, which, for a large array would make the URL quite long. ... There shouldn't be a limitation on the size, http 1.1 should allow any size as long as the server manage that, otherwise you get an error message. ... each loop to set the $_SESSION array. ... session size is limited by the servers storage, but as soon as you have got the data to the server it's there, no matter if you have session or not, session is better for store data between scripts. ...
    (alt.php)