What are the scopes in Portlet scopes?

Portlet containers provide the PortletSession object so you can store user-specific
data across portlet requests. PortletSession is similar to HttpSession, and it provides
methods to maintain session attributes, get and set the maximum interval of
time for which the session can remain inactive, get PortletContext, and so on. Just as
each web application has a unique HttpSession per user, each portlet application has
a unique PortletSession per user.


PortletSession is different from HttpSession because PortletSession provides you
with two different scopes to store session attributes, identified by the constants
APPLICATION_SCOPE and PORTLET_SCOPE in the PortletSession interface.


 Http-Session doesn’t have the concept of scoped attributes