206810 - No LAST-MODIFIED element in the ical of generated events or tasks

Status: RESOLVED FIXED

(Calendar :: Internal Components, defect, P1)

Description

[Patrick Gerzanics]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; YComp 5.0.0.0)
Build Identifier: 1.3.1 (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425)

In order to handle synchronization cleanly between the Mozilla Calendar's 
events and a collaboration server, some sort of element must be present to 
specify when an item was last modified.  According to the ical standard, this 
element is 'LAST-MODIFIED' and should be of a typical DATE-TIME format.

Property Name: LAST-MODIFIED

   Purpose: The property specifies the date and time that the
   information associated with the calendar component was last revised
   in the calendar store

Description: The property value MUST be specified in the UTC time
   format.

Without this information, synchronization is exceedingly inefficient because 
all items must be sent each synch cycle.

Reproducible: Always

Steps to Reproduce:
1.  Create an event and note the DTSTAMP time
2.  Modify that event

Actual Results:  
Note that the DTSTAMP element did not change, nor is there a LAST-MODIFIED 
element.


Expected Results:  
Either the DTSTAMP element should change, or a LAST-MODIFIED element should be 
present with the time of the modification.

Comment 1

[Mike Potter]

If this helps someone do synching, then let's do it as quick as possible.

Comment 2

[Mostafa Hosseini]

Fixed in cvs:
http://bonsai.mozilla.org/cvsview2.cgi?file=oeICalImpl.cpp&branch=&root=/cvsroot&subdir=mozilla/calendar/libxpical&command=DIFF_FRAMESET&rev1=1.66&rev2=1.67

Comment 3

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!