Closed Bug 431127 Opened 12 years ago Closed 11 years ago

Move email-specific itip processor code to the transport

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Fallen, Assigned: dbo)

References

Details

(Followup from bug 428392)

We have some locations where transport specific things happen. For example:

>Index: calendar/base/src/calItipProcessor.js
>+        // TODO This is email specific -> Move to transport
>         // When replying, the reply must only contain the ORGANIZER and the
>         // status of the ATTENDEE that represents ourselves. Therefore we must
>         // remove all other ATTENDEEs from the itipItem we send back.
>         if (respMethod == "REPLY") {
>             // Get the id that represents me.
>             // XXX Note that this doesn't take into consideration invitations
>             //     sent to email aliases. (ex: lilmatt vs mwillis)
>-            var me;
>-            var idPrefix;
>-            if (transport.type == "email") {
>-                me = transport.defaultIdentity;
>-                idPrefix = "mailto:";
>-            } else {
>-                throw Components.results.NS_ERROR_NOT_IMPLEMENTED;
>-            }
> 
>             var attendees = newItem.getAttendees({});
> 
>             for each (var attendee in attendees) {
>                 // Leave the ORGANIZER alone.
>                 if (!attendee.isOrganizer) {
>                     // example: mailto:joe@domain.com
...


Some work was already done, getting the scheme from the transport for example. If it turns out to be impractical to automatically insert a ":" between |transport.scheme| and the attendee address, then this could be changed to.
Depends on: 457203
I think this is finally fixed with bug 457203.
Assignee: nobody → daniel.boelzle
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
You need to log in before you can comment on or make changes to this bug.