html5-img
1 / 3

Scalability and simultaneously maintaining availability, security and traceability is hard

Middleware for dependable synchronisation and persistence of distributed workspaces Santosh Shrivastava School of Computing Science Newcastle University, UK santosh.shrivastava@ncl.ac.uk. Scalability and simultaneously maintaining availability, security and traceability is hard

meredith-pugh
Download Presentation

Scalability and simultaneously maintaining availability, security and traceability is hard

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Middleware for dependable synchronisation and persistence of distributed workspacesSantosh ShrivastavaSchool of Computing ScienceNewcastle University, UKsantosh.shrivastava@ncl.ac.uk

  2. Scalability and simultaneously maintaining availability, security and traceability is hard • collaboration protocols are full of non-determinism (time out events) • ensuring that each party has consistent state of the on-going interaction - despite possible misbehaviour by others - is difficult • Possible solutions will need to be based on borrowing ideas from group communication, replica management developed within the middleware community and fair exchange and non-repudiation ideas developed within the security community

  3. Non-repudiable Interactions • Information Sharing • Multi-party, peer-peer interaction • For an update proposed by A: • B and C need evidence that update originated at A (NRO update) • A needs evidence that B and C received the update (NRR update) • A, B and C need evidence that, after update, the information will be in a consistent, agreed state (NRO agreement, NRR agreement) B update i update A update C

More Related