Re: Preserving data within a whole application.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You aren't actually looking for servlet functionality but application level
state? Cache or Application could help with that

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke


"Omega" <atrauzzi@xxxxxxxxx> wrote in message
news:1146316796.376526.92380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I just recently recieved my full copy of Visual Studio 2005
(excited!!!), and have gone head first into writing my first
application.

Sadly, I've hit a design barrier.

From what I can see, ASP.NET 2.0 has no facility that is instantiated
upon deploying an application - similar to servlets. I don't really
need the functionality of a servlet, but what I am interested in
getting is an "always on" class that exists between different requests
between different ASP.NET classes.

My first instinct is to create some static monster class that has all
my functionality and that will persist for the duration of the whole
ASP.NET application's life. Although something in my gut tells me that
static classes are not to be abused in such a way.

Does ASP.NET provide me with anything that I can use to share
information between aspx pages and web service classes? On top of
that, what would be the best way to write a totally non-visual class
that is responsible solely for my "business logic"? The idea is that
after writing this omnipresent workhorse class, I'll use aspx pages,
web service pages and anything else to make use of the same set of data
without having to hit a database for small tidbits of session data.

(I'm writing a very simple user login system, and while I'm aware of
ASP.NET's built in user handling, I would like to write my own system
and then work it into ASP.NET's system afterwards.)



.

Relevant Pages

  • Re: comparison between portability libraries?
    ... most of these offer functionality that is imo a minor issue to ... glib contains code for all kind of data structures, ... before (writing both the client code and a server). ... a years worth of coding (maybe a year coding on average for about 4 ...
    (comp.lang.misc)
  • Re: Some Advice Please
    ... Sorry to bother you all, i'll repost in .net general discussions. ... Except for some of the specific functionality, ... describing sounds a lot like writing an email program ...
    (microsoft.public.vb.general.discussion)
  • Writing Application "Drivers"
    ... currently writing a C# Windows Forms application. ... I have a case where an application needs some functionality that varies depending on the current data. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: dr Lisp
    ... doing so would be pretty easy - if you'd spent as much time writing them as you have writing posts in this thread you'd be a good way toward finished already. ... IOW, the hard part of a lisp editor is the funtionality that navigates around sexps, makes selections, copies, cuts, pastes, enters keystrokes literally at point, etc. ... Below are links to the editor command reference section of the editor users guide. ... It's simply a matter of writing a bunch of editor:defcommand and editor:bind-key forms to associate functionality to keys. ...
    (comp.lang.lisp)