A calendar web app demo built for a distributed architecture which enforces information flow policies.
The application will not build unless you first configure the build.properties file in etc, which you
should set to your path to $FABRIC
What kind of policy do we want for the session actions to work correctly? Had not thought about this until yesterday/today when finally able to get past a few compiler bugs that led me to these bugs...
Are keystores autogenerated?
Questions regarding the persistence of store objects, what happens when the store is turned off. How does the java object retain its state? Or is this object in essence completely something else? I'm not familiar with the BerkelyDB
What is the property: fabric.dissemination.pastry.pastry_socket_allow_loopback=true
- https://www.cs.cornell.edu/people/egs/615/pastry.pdf
- https://www.freepastry.org/FreePastry/README-1.3.html
There is no fabric.util.Date object - FIXED!
← → ⊥ ⊤
Top principal can write (integrity)
- old syntax: {*!:}
- new syntax: {⊤←}
Top principal can read (confidentiality)
- old syntax: {*:}
- new syntax: {⊤→}