Application state

Front-end/Back-end state

PoP is well suited for CRUD (Create, Read, Update, Delete) applications. It keeps its state quite simple, directly in the front-end for Read operations, or going to the back-end and have the response update the state in the front-end for Create/Update/Delete operations. Since there is no dual, independent front-end/back-end state, there is no need to synchronize the state between these.

recommend

Recommending a post first executes the operation in the back-end, and the response will update the state in the front-end

User’s state

The PoP application does not restrain the user from being logged in or not, it will cater for both states at every moment. This is accomplished by classifying all pages in the website as either: requiring user state (such as “Edit my account” or “My posts” pages), or not (such as the homepage, or the “Posts” page). When the user requests a page requiring user state, he/she will be asked to log-in, and only then the corresponding data will be loaded. At any moment, the user can open several pages on the website, both requiring and not requiring user state; after he/she logs out, PoP will close only those pages requiring the user state, and destroy all associated information, all without doing a redirect to another page.

As such, it can be said that a PoP application, instead of having two user states:“logged in” and“not logged in”, it has a unique user state that can be called: “in permanent transition between ‘logged in’ and ‘not yet logged in’”.

userstate

Several pages can be open simultaneously, both requiring user state (“My Content”) or not (“Home”). When the user logs out, only those pages requiring user state will be closed.


Welcome to the PoP framework!
Break the information monopoly

the PoP framework is open source software which aims to decentralize the content flow and break the information monopoly from large internet corporations. Read more.


Sign up to our newsletter: