Closed Bug 699280 Opened 13 years ago Closed 12 years ago

Adapt to the calIChangeLog interface changes (wcap offline support)

Categories

(Calendar :: Provider: WCAP, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Fallen, Assigned: Fallen)

References

Details

Attachments

(2 files)

+++ This bug was initially created as a clone of Bug #697553 +++

Since offline support has landed, both gdata and wcap need some updating. This bug covers wcap support.

First of all, here is a patch that just disables the cache for wcap in total. I know this sucks, but before I break a provider in total I'd rather provide a workaround that successfully migrates users for the time being.

I've tested the upgrade path from cached to no cache and its not noticeable. As soon as the real fix lands, users are then auto-upgraded to using the cache again on restart.
Comment on attachment 571501 [details] [diff] [review]
[checked in] Disable the cache - v1

I'm going to go this route for the release to make sure I'm not rushing in more big features. Leaving the bug open for the real patch, which should make the next release in 7 weeks.

comm-central changeset cda39712fdae
releases/comm-aurora changeset 01a98a8c26a5
releases/comm-beta changeset c47c0a0a785e
Attachment #571501 - Attachment description: Disable the cache - v1 → [checked in] Disable the cache - v1
Hello WCAP Folks,

as mentioned in my previous comment, unfortunately I cannot enable the cache in the next release. I'd be interested to hear how many users are behind your WCAP system and how many of them use Lightning. Is Thunderbird/Lightning managed by your IT department, and if so how is the update policy?

For the release you will have two options:
* Do nothing and the cache will be temporarily disabled.
* Stay with the last release until this bug is fixed

Let me know how this works out for you. Also, if you can convince your mangement to invest developer resources into Lightning this would be marvelous. WCAP currently works, but since its not in my primary focus I can't forsee if any new server patchlevels break the provider and as you've seen before with bug 679669, platform changes that break WCAP might also creep in unannounced.
(In reply to Philipp Kewisch [:Fallen] from comment #2)

Philipp, I sent you a mail about our use of WCAP at your registered mail address in bugzilla, but I wonder whether this address is a technical one or a real personal one.
Laurent, I recevied your email and will reply soon. Thanks for the infos!
At my work, we use this functionality(wcap offline support) since about 1 year because we have network problem. When I'm disconnected, I loose everything.

When do you plan to enable the cache again.

Thanks for your help.
If I get to pick, then I'd rather like to do some changes to the offline interfaces, which might make adaptions to wcap unneeded or very minimal.

Also, thanks for commenting. That reminds me I need to reply to an email!
Hi Philipp,

Still waiting for your work ... ;-)
When do you plan to do it ?
Hi Philip,

I've got no answer from you ....
Will you enable the cache again for wcap ?

Now I use TB 7.0 and Lightning 1.0b7 to keep the cache functionality.

Thx for your response and have a good day.
Hi! I have a patch almost working that changes the offline API so that no further methods are needed, which means the cache can be enabled again.

It still needs some testing and I need to find out if a certain case will cause an endless loop or not.

I haven't opened a bug for it yet, but I'll make it block this one so you are in the loop.
This patch fixes the calIChangeLog listener implementation and requires a nightly with bug 756052 applied (tomorrow).

One thing I noticed is that cached WCAP is also showing symptoms of bug 717067, but I think its more minor, the main thing is to get this running.
Assignee: nobody → philipp
Attachment #647137 - Flags: review?(mohit.kanwal)
Comment on attachment 647137 [details] [diff] [review]
Fix calIChangeLog Implementation - v1

Review of attachment 647137 [details] [diff] [review]:
-----------------------------------------------------------------

Looks alright to me, a couple of style fixes. How to test. Is there a WCAP version available online for testing? and looks like I need to look into bug 717067 pretty soon.

::: calendar/providers/wcap/calWcapCalendarItems.js
@@ +583,4 @@
>              }
>              var items = this_.parseItems(icalRootComp, calICalendar.ITEM_FILTER_ALL_ITEMS,
>                                           0, null, null, true /* bLeaveMutable */);
> +            if (items.length != 1) {

Should we collapse the two cases? one is a Components.Exception the other is just a console error.

@@ +1324,1 @@
>      var this_ = this;

you can use this opportunity to correct the vars into let ;)
Attachment #647137 - Flags: review?(mohit.kanwal) → review+
I'd like to leave the wcap provider alone as much as possible. If I start fixing nits on it then I will end with regressions and need start doing large scale changes.
comm-central changeset 7155880be5bb
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.9
You need to log in before you can comment on or make changes to this bug.