34 |
|
|
35 |
Research has been done in a number of areas to alleviate this problem. |
Research has been done in a number of areas to alleviate this problem. |
36 |
There are a number of proposals for sharing a web browser's cache |
There are a number of proposals for sharing a web browser's cache |
37 |
between users [search for refs!]. |
between users [squirrel]. |
38 |
... |
... |
39 |
Thompton and De Roure [ref ht'01] propose a peer-to-peer system |
Thompton and De Roure [ref ht'01] propose a peer-to-peer system |
40 |
for discovering cached web resources in a mobile, disconnected setting, |
for discovering cached web resources in a mobile, disconnected setting, |
137 |
I'd prefer term 'replication' instead of term syncing, when |
I'd prefer term 'replication' instead of term syncing, when |
138 |
updating data to 'the most recent state'. E.g. Lotus Notes uses |
updating data to 'the most recent state'. E.g. Lotus Notes uses |
139 |
term replication, when one performs locally made updates into |
term replication, when one performs locally made updates into |
140 |
a centralized server --> 'used within same system'. Syncing term, however, is used when importing/exporting |
a centralized server --> 'used within same system'. Syncing term, however, |
141 |
e.g. Nokia Communicator calendar data into/from Lotus Notes calendar --> 'used between different systems'. |
is used when importing/exporting e.g. Nokia Communicator calendar data into/from |
142 |
|
Lotus Notes calendar --> 'used between different systems'. |
143 |
|
|
144 |
|
|
145 |
hemppah: worth to mention is that Ray Ozzie is a man behind Lotus Notes and Groove; Lotus Notes |
hemppah: worth to mention is that Ray Ozzie is a man behind Lotus Notes and Groove; |
146 |
is based on client-server model and, Groove is based on p2p model --> possible direction etc. ? |
Lotus Notes is based on client-server model and, Groove is based on p2p model --> |
147 |
|
possible direction etc. ? |
148 |
|
|
149 |
|
hemppah: I think we should mention that in Gzz one refer to data in non-hierarchial |
150 |
|
way, where as in Notes (and other systems also, references!!), we must use |
151 |
|
hierarchial way. In Notes |
152 |
|
1) every document has a unique identifier, which is unique among all replicas |
153 |
|
of database |
154 |
|
2) every document/design element has a identifier, named as noteID, which is unique |
155 |
|
in database, but not among all replicas of database |
156 |
|
3) every view has a unique identifier, which is unique among all replicas of |
157 |
|
database |
158 |
|
4) every database has a ID, named as replicaID, which identifies database's replicas |
159 |
|
among all databases |
160 |
|
|
161 |
|
So, if we want to refer to a document, we use format: |
162 |
|
|
163 |
|
replicaID/viewID/documentID |
164 |
|
|
165 |
|
Also, we can refer to same document, through *many different* views: |
166 |
|
replicaID/viewID1/documentID |
167 |
|
replicaID/viewID2/documentID |
168 |
|
|
169 |
|
Notes://server/D235632D00313587/38D22BF5E8F088348525JK7500129B2C/REWB3FDE0D53807B67C2256CB50026FCVV |
170 |
|
|
171 |
|
Where in Gzz, we don't know the location, we know only the *identify*, like this |
172 |
|
|
173 |
|
urn-5:FAB3FDE0hgfD5kkjj3807B67C2256CfsdB50026FC51 |
174 |
|
|
175 |
|
Above is not a *correct* urn-5, but very similar to last part of notes' syntax. |
176 |
|
|
177 |
|
(Of course, this is very similar to 'normal' URLs, but our purpose here is to give an example |
178 |
|
of how one refer to a particular data item in colloboration-like tool, like Notes) |
179 |
|
|
180 |
|
Of course, in Notes, there are servers, which maintain replication of data, opposite to Gzz. What is |
181 |
|
interesting in Notes' replication, is the fact that the replication of database not only |
182 |
|
replicate the *data* but also design of data, which represent the data. |
183 |
|
Worth to mention is also that, even if the data and the design of data (logic etc.) is |
184 |
|
in the *same* (physical) structure, data and design of data is very loosely coupled with |
185 |
|
each other. |
186 |
|
|
187 |
|
Additionally, worth mention is that how things are going towards non-hierarchical reference models, |
188 |
|
for instance, Notes and Gzz, which both are based on the same Xanalogical model. |
189 |
|
|
190 |
|
|
191 |
"Usability in the face of intermittent connectivity" is |
"Usability in the face of intermittent connectivity" is |