stateless

If I have a stateless view in JSF containing a form. How does the different phases will behave when I filled out the form and submit it? since the state of the view is not stored anywhere, how does the phases "appy request values", "update model" etc. will work now? BalusC All phases of the JSF lifecycle will continue to run. Only the restore view and render response phases will behave a bit differently. The restore view phase will now only build the view, but not restore its state. The render response phase will now only render the view, but not save its state. That's basically it. All other

Hibernate has a Stateless Version of its Session : Does something similar exist for the JPA EntityManager? I.e. an EntityManager that does not use the first level cache? Not part of the JPA API or spec. Individual implementations may allow disabling the L1 cache. DataNucleus JPA, the one I have used, does allow this From JPA point of view: javax.persistence.EntityManager stands for 1st level cache (persistence context, transactional cache) javax.persistence.EntityManagerFactory stands for 2nd level cache (shared cache) A given persistence provider may implement additional caching layers.

I'm struggling with the concept of how to design a stateless RESTful authentication API with multi-factor authentication. Almost by definition, the need of a 2FA requires multiple states; logging in with a username/password, then submitting a "code" (either a TOTP, SMS-code, answer to a verification question, etc). This further implies a finite-state-machine (FSM) of some sort. As far as I can tell, the only options which exist in order to maintain a stateless mechanism are: the client must transmit some state information (ex: current FSM state) when submitting data to transition to the next

Stateless是一个基于C#创建状态机的简单库 .Net轻量状态机Stateless 很多业务系统开发中，不可避免的会出现状态变化，通常采用的情形可能是使用工作流去完成，但是对于简单场景下，用工作流有点大财小用感觉，比如订单业务中，订单状态的变更，涉及到的状态量不是很多，即使通过简单的if-else也能足够使用，甚至是用上switch去减少if-else的使用，都是可以的，尽管这会丧失某些东西。为更好的优化整个流程，此时会考虑到使用状态模式来解决一些问题。 　　Stateless状态机GitHub： https://github.com/dotnet-state-machine/stateless 一、状态模式与状态机 1、状态模式："允许一个对象在其内部状态改变时改变它的行为。对象看起来似乎修改了它所属的类 "。 (State Pattern: "Allow an object to alter its behavior when its internal state changes. The object will appear to change its class ".) 　　对于这个定义，有点抽象，变通理解一下可以这么理解：状态拥有者将变更行为委托给状态对象，状态拥有者本身只拥有状态(当然也可以抛弃状态对象)，状态对象履行变更职责。 2、状态机："依照指定的状态流程图

The stateless web application seems promising . How to make one? Especially with Spring WebMvc? Any guidelines? Here are a few things on my mind: Avoid creating session Use a centralized storage for state info and share that among web application instances. ADD 1 I think it is not a question of whether to keep state info or not. State info is always necessary if you want to do something useful. It is actually a question where/how to keep the state info. This article is useful. It mentioned in-proc/out-of-proc session, data cache, and why not to use session. Related: Use Spring MVC for