Calendar servers often store their events in RDBMS or other similar
backends, yet calendar servers are required to store all the X-
properties (all the extensions) inside iCalendar resources. WebDAV
servers, also commonly built on databases, have to store custom
client-defined properties (e.g. in XML, while preserving namespaces
and stuff). It's a little different in the details in the Atom
situation but the same kind of coding problem.
Lisa
On Jun 14, 2006, at 3:36 PM, Bill de hÓra wrote:
Lisa Dusseault wrote:
(Personally I feel it's a mistake not to require servers to store
extension elements. Yes, it's work for the server, but think of
how this could be used in 10 years if it's as successful as I
suspect it will be. Many conceivable extensions can work between
clients, with no new code required on servers, provided the server
faithfully stores and provides the extension data as part of the
feed/entry.)
Speculation: a key (har har) reason impls will tend to drop
extensions is due to RDBMS storage. Anyone got a good mysql schema
for key/value pairs fk'd to an Entry table?
cheers
Bill
