We found that the UIP Block caches object known as a
sessionMoniker in the ASP.NET session object. This object
includes the TaskID, currentGraph and currentView. These
items are also held in the State object.

So the storage is redundant and if you try to avoid
ASP.NET Session object dependency but using some other
persistence provider, you still have a dependency on the
ASP.NET Session.

Also we found that if someone tries to use foward or
backward navigation, the UIP Block notices this from the
currentView in the sessionMoniker and then redirects the
browser to the currentView. If you want backward -
forward navigation in your app, you will need to rewrite
parts of the UIP.

Otherwise the UIP is a timesaver.