stateless

It seems some web architects aim to have a stateless web application. Does that mean basically not storing user sessions? Or is there more to it? If it is just the user session storing, what is the benefit of not doing that? tster Reduces memory usage . Imagine if google stored session information about every one of their users Easier to support server farms . If you need session data and you have more than 1 server, you need a way to sync that session data across servers. Normally this is done using a database. Reduce session expiration problems . Sometimes expiring sessions cause issues that

I come from Play!framework. Very much like it's stateless architecture. Say the session concept is different from the class Java Servlet's HttpSession. Session in Play can store very limited string typed attributes, which is serialized to the browser. Any stateful object is stored either in cache (which can be easily distributed with memcached impl) or database directly. User app can get the stateful objects via a unique session id. This structure makes it very easy to implement a cluster of Play's application. I am curious how to implement such a stateless application in Spring MVC framework.

I would like to know, what are the principal differences between : javax.enterprise.context.SessionScoped and javax.ejb.Stateful javax.enterprise.context.ApplicationScoped and javax.ejb.Singleton I know that a @SessionScoped and a @Stateful allows to create a new instance for each client. I also know that for the @ApplicationScoped and @Singleton / @Stateless they are shared between the clients. => But when should I consider it's better to choose an EJB, or the other? @SessionScoped denotes a scope while @Stateful is in a way what we would now call a stereotype. @Stateful adds a number a

I've been working with Wicket for month or two now, making simple web applications with it and getting used to models and so forth. Now I'd like to move forward and see if I can put what I've learned so far to use and create a medium/large web application. However, I haven't spent much time thinking about how to make pages stateless. If I understand correctly, making a stateless page is achieved by making the page bookmarkable and making sure that no stateful components are added to the page. For the website I am making I want to avoid "Page expired" messages, let users be logged in via

There are lots of guidelines, sample codes that show how to secure REST API with Spring Security, but most of them assume a web client and talk about login page, redirection, using cookie, etc. May be even a simple filter that checks for the custom token in HTTP header might be enough. How do I implement security for below requirements? Is there any gist/github project doing the same? My knowledge in spring security is limited, so if there is a simpler way to implement this with spring security, please let me know. REST API served by stateless backend over HTTPS client could be web app, mobile

This question already has an answer here: How do I make my Web Application stateless yet still do something useful? 5 answers I know that there are many discussions on difference between stateful app and stateless app, and that stateless is what function programming language does, every function call with the same args will return the same value. Does it mean object-oriented language is not able to make a fully stateless application,since every object will typically have state. Also, in Java web application, we typically need to trace user state,and which is solved by session. But how to do