Indeed which is why web applications exist as constructs on top of the web that live to provide stateful interaction through a stateless medium.
On Jan 6, 11:15 am, "Eric W. Brown" <[email protected]> wrote: > The web is defined as 'stateless' because everything in memory gets dumped > between > Requests and you have to do work to preserve state (like storing it in the > DB, session etc) > > Not because it's impossible to preserve state, but because it's not for free > like a > Regular executable. > > Cal- > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Chris Marisic > Sent: Wednesday, January 06, 2010 10:11 AM > To: nhusers > Subject: [nhusers] Re: Long conversation ASP.NET MVC > > I might be reading too much into your statement and perhaps minimizing your > bridge of NH and web, but obviously the web is stateless however web > applications are not. If web applications were truly stateless NH wouldn't > even have a purpose on the web since it's a wrapper to a construct that > allows the web to have state (ie a database) > > On Jan 6, 9:14 am, Jason Meckley <[email protected]> wrote: > > I think the biggest > > issue developers have with NH and web is simply understanding the web > > is stateless and the desktop is stateful. once that is understood, and > > embraced, it's much easier to develop the application.
-- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
