Bob Wyman wrote:
Basically, there are many really easy ways that one can handle
streams of Atom entries. You could prepend an empty feed to the head of the
stream, you could use "virtual" end-tags, you could just send entries and
rely on the receiver to wrap them up as required, etc... But, since all of
these are really easy and none of them really gets in the way of anything
rational that I can imagine someone wanting to do, why not just default to
doing it the way it is defined in the Atom spec? In that way, we don't have
to create one more context-dependent distinction between formats. Complexity
is reduced and we can avoid having to read yet-another-specification that
looks very, very much like hundreds we've read before. If Atom provides all
we need, lets not do something else unless there is a *very* good argument
to do so.
bob wyman
+1. The basic format gives us everything we need to enable this. Even
looking back over my PaceSimpleNotify proposal.. in which I introduce a
notification element used to identify the action that has occurred on
the element (e.g. create, update or delete), I can see that there really
is no need to have that element.
- James
