Permalink
Browse files

mehr

  • Loading branch information...
1 parent 288d360 commit 2bbb53e2b643029e3f36579801b1d1881679d29a @thkoch2001 committed Apr 3, 2012
Showing with 9 additions and 24 deletions.
  1. +9 −8 latex/restful_groupware.tex
  2. +0 −16 notes.org
View
17 latex/restful_groupware.tex
@@ -1876,7 +1876,7 @@ \section{Implementation}
\subsection{Control Flow Overview}
\label{sec:overview}
-% @TODO Hier fehlt der Überblick über die gesamte Anwendung ein bisschen
+% Schreier: Hier fehlt der Überblick über die gesamte Anwendung ein bisschen
\autoref{fig:executionflowoverview} outlines the most important classes for the
control flow. Jersey routes calls to the four different ``Jersey Resources''
@@ -2008,7 +2008,7 @@ \subsubsection{Resource properties}
\subsubsection{Resource life cycle}
\label{sec:resource-life-cycle}
-% @TODO visualisieren?
+% schreier: visualisieren?
Resource classes in this work have a four staged life cycle. The first stage is
represented by the \lstinline:UnparsedResource: class, instantiated by the
@@ -2826,13 +2826,14 @@ \subsubsection{JSON based media types for collections}
Unfortunately, Collection+JSON in its current state is not yet fully usable to
implement the interactions described in \ref{sec:interactions}.
-Collection+JSON does not enforce an order of the elements in a collection. The
-proposed synchronization interaction however is based on the assumption that the
+Collection+JSON does not enforce an order of the elements in a collection or at
+least the notion that collections can be paginated with a \lstinline:next:
+link-relation and that consecutive feeds respect an ordering. The proposed
+synchronization interaction however is based on the assumption that the
collection feed is ordered by the time of the last modification. Consequently,
-there is also no equivalent to an ATOM
-``deleted-entry'' \cite{draft-snell-atompub-tombstones-14}, which enables the use
-of an updates feed for synchronization.
-% @TODO wenn man entsprechende Filter anbietet ist die Sortierung nicht mehr unbedingt relevant
+there is also no equivalent to an ATOM ``deleted-entry''
+\cite{draft-snell-atompub-tombstones-14}, which enables the use of an updates
+feed for synchronization.
The facility to include full item representations directly in the collection
(the ``data'' property) is restricted to simple key/value pairs. This excludes
View
16 notes.org
@@ -83,16 +83,6 @@ Vorstellung der Medientypen inkl. Hypermediaunterstützung
- HTML
- the semantik of links in PoCo/vCard/iCal is defined by the field (property) where they appear.
-** Wie viel muss ein Client vorher wissen?
-
- - Standard
- - Der Client muss die Medientypen verstehen, inkl. OpenSearch, PoCo
- - Der Client muss die zur semantischen Annotation verwendeten Schemata kennen
- - Noch kein Standard, aber bald: Atom deleted entry
- - Der Client muss alle weiteren genutzten IETF bzw. W3C standards implementieren
- - Keine Standards
- - Der Client muss eine link relation auf eine HTML Form zum Anlegen neuer Resourcen kennen
- - Der Client muss die zur typisierung von Collections verwendeten Atom Categories verstehen
* Persistency for Groupware Data
Relational Databases vs. NoSQL databases vs. plain files
@@ -122,12 +112,6 @@ Relational databases are not practical for contacts, events or todos. Common pat
% The life cycle of a CollectionStorage is across individual requests to facilitate caching or database connection reuse.
-* Synchronization
-
-Portable Contacts has a filter ``updatedSince''.
-
-How is synchronization done in CardDAV?
-
* Media Types
\section{Media Types}

0 comments on commit 2bbb53e

Please sign in to comment.