StateFull or StateLess

[david_navigator]

I've not done any clever web design for a very long time. 

Looking at the spec for uniGUI I see
 

 uniGUI Web application framework makes developing stateful Web applications easier than ever

 

 

however looking at the spec for TMS's web core I see

 

with Tms web core and jqwidget it''s stateless

 

 

so what's the practical difference between stateful & stateless as far as the developer is concerned ?

 

David

[Ron]

Stateful and stateless refer to the software's ability to store and remember

current state in a sequence of events, like being logged in or not.

 

As I understand Unigui it is inherently stateful, in the sense that you always

have to go through the creation of a mainModule which has a session object

and all forms are created on the fly from the mainModule instance.

 

So there is no isolated access to a form, as it always is a child of the

mainModule, which stores state information.

 

With Web Core there are only html, css and js, and you can access

pages directly, not necessarily being dependent on the loading of

some other layer or some other code already running.

 

But even if Unigui works like this, it may behave pretty much stateless,

as you can use parameters to direct the user to specific forms, and

it is up to you if you want to have a login or not.

 

And of course Web Core have stateful capabilities, like being able to

save session data and keep track of logged in status etc. I have not

checked this, but what is the point of making a stateless webapp,

it is almost an oxymoron. The whole point of a webapp is to circumvent

the stateless limitation of the http protocol, so we get closer to the

traditional desktop functionality, but in a client/server environment.

[david_navigator]

Thanks delpihdude - that makes perfect sense.
I'm just at the bottom of the web app learning curve so lots to learn and I think unlearn from my normal delphi way of working.

[Tokay]

This discussion about differences is interesting:

https://stackoverflow.com/questions/5329618/stateless-vs-stateful-i-could-use-some-concrete-information

[rahul]

Both Stateful and Stateless omnipresent in IT shops. But modern software being architected in the Stateless manner since scaling is an essential factor for today’s world.

[Sherzod]

5 minutes ago, rahul said:

Both Stateful and Stateless omnipresent in IT shops. But modern software being architected in the Stateless manner since scaling is an essential factor for today’s world.

Hello,

Are you using UniGUI?

[Ron]

Only the simplest webapps are completely stateless, as far as I know.

There are two basic ways to store state:
1) on the server, using session control with session data stored on the server
2) on the client, as a session identifier passed in the URL back and forth

The second option is what they call stateless, as state is not stored on the server
but on the client, so it is really not stateless per se. Please correct me if I am wrong.

With Unigui you can do both, but since every form takes an initial loading of
a MainModule, it may not be as efficient as with e.g. TMSWebCore, where
you only have a bunch of html, css and js files to load.

With good webserver preloading and caching you may come close, though.