541 |
|
|
542 |
Review of the use cases: what does storm in each? |
Review of the use cases: what does storm in each? |
543 |
------------------------------------------------- |
------------------------------------------------- |
544 |
(where&how to put this, if use cases are used like this at all?) |
(where&how to put this, if use cases are used like this at all? |
545 |
|
agreed with benja on irc that we might try this approach - hinting about the |
546 |
|
use cases early on and taking a detailed look later, in light of the design.) |
547 |
|
|
548 |
1. live meeting: |
1. live meeting: |
549 |
Documents have been assigned block-ids (and urns?) at creation. |
Documents have been assigned block-ids (and urns?) at creation. |
551 |
network. (...) |
network. (...) |
552 |
|
|
553 |
2. syncing via a remote connection after working separately: |
2. syncing via a remote connection after working separately: |
554 |
Both new versions are actually diffs to the original. How do they merge? |
Both new versions are actually diffs to the original. Merging is |
555 |
|
application-specific. |
556 |
|
|
557 |
3. publising on/from the laptop: |
3. publising on/from the laptop: |
558 |
B sets the document public (how that is done depends on UI implementation), |
B sets the document public (how that is done depends on UI implementation), |
559 |
.. how does it go with storm, then? |
i.e. putting in a published pool, which may reside locally or externally |
560 |
|
e.g. on a (dedicated) server that is "always-on". These public/private zones |
561 |
|
are an area where future research is needed, possibly related to rights and |
562 |
|
permissions etc. too. |
563 |
|
|
564 |
4. A and other people viewing, commenting, bookmarking, linking: |
4. A and other people viewing, commenting, bookmarking, linking: |
565 |
When someone views the document, the system retrieves the datablock. |
When someone views the document, the system retrieves the datablock. |
566 |
Comments may be new entities(?) linking to it, editing would create a new |
Comments may be new entities(?) linking to it, editing would create a new |
567 |
version as a diff as a new datablock with a new guid. Bookmarks and links to |
version as a diff as a new datablock with a new guid. Bookmarks and links to |
568 |
the original are made to the ID of the original, with no trace of the |
the original are made to the ID of the original, with no trace of the |
569 |
location (originally B's laptop). |
location (originally B's laptop). (more info about pointers here, and in the |
570 |
|
next one?) |
571 |
|
|
572 |
5. When B takes her laptop off-line, the searches for the ID of her (and |
5. When B takes her laptop off-line, the searches for the ID of her (and |
573 |
A's) Document simply result pointing at the other copies (e.g. on A's |
A's) Document simply result pointing at the other copies (e.g. on A's |
578 |
hosts. (does storm actually do this / is it aimed at this?) |
hosts. (does storm actually do this / is it aimed at this?) |
579 |
|
|
580 |
7. When B reconnects, can check comments to the Document etc? How does that |
7. When B reconnects, can check comments to the Document etc? How does that |
581 |
happen? |
happen? Index? |
582 |
|
|
583 |
8. Experience and future directions |
8. Experience and future directions |
584 |
=================================== |
=================================== |
585 |
|
|