[Cosmo-dev] Cosmo 0.6 object model changes
bcm at osafoundation.org
Tue Nov 14 11:20:00 PST 2006
On 11/14/06, Randy Letness <randy at osafoundation.org> wrote:
> That works until you have to store property names or values that are
> bigger than what the index table can handle. We truncate values in the
> index table and ignore property names. To be 100% icalendar compliant
> we would have to use text fields to store the key/value pairs, which
> prevents efficient indexing/searching.
ok. then lets stick with the blob and indexing that we have now. when
a calendar item is updated, we'll have to rewrite both the blob and
> Does Chandler care about a file that is created using DAV? I thought
> all Chandler cared about was Notes,Events,Tasks, and Messages. So if a
> DAV client creates a .jpg in a shared collection does Chandler even want
> to know about it? Do we even allow this?
we support it now. chandler shouldn't have any problem with it - we'll
just be sending a content item record over morse code.
More information about the cosmo-dev